Amp

Bridge Amp to LLMRPM through a local CLIProxyAPI proxy.

Configuration

SettingValue
API shapeAnthropic-compatible
Base URLhttps://llmrpm.com/api
AuthAuthorization: Bearer llmrpm_...
  • Create a CLIProxyAPI config.yaml with an llmrpm custom provider.
  • Set provider base-url to https://llmrpm.com/api/v1 and api-key to your LLMRPM key.
  • Map Amp's requested model names to LLMRPM public model IDs under model-mappings.
  • Start the local proxy on http://localhost:3456, then point Amp's ANTHROPIC_BASE_URL at that proxy.

Example

config.yaml
server:
  port: 3456

custom-providers:
  - name: "llmrpm"
    base-url: "https://llmrpm.com/api/v1"
    api-key: "llmrpm_YOUR_KEY"
    models:
      - "claude-sonnet-5"
      - "claude-haiku-4.5"

model-mappings:
  gpt-5.4:
    provider: llmrpm
    model: claude-sonnet-5
  gpt-5.6-sol:
    provider: llmrpm
    model: claude-sonnet-5
  glm-5:
    provider: llmrpm
    model: claude-haiku-4.5

force-model-mappings: true
Docker
docker run -d --name cliproxyapi \
  -p 3456:3456 \
  -v ./config.yaml:/CLIProxyAPI/config.yaml \
  eceasy/cliproxyapi
Shell
export ANTHROPIC_BASE_URL="http://localhost:3456"
export ANTHROPIC_API_KEY="llmrpm_YOUR_KEY"

amp

Troubleshooting

SymptomCause & fix
Proxy not startingVerify Docker is running with docker ps, then check the container logs for a config parse error.
Authentication errorCheck that the API key has no extra spaces and has not been revoked in the dashboard.
Model rejectedUse a public model ID returned by GET /api/v1/models; do not use display names or aliases.
Connection issueConfirm the configured base URL is exactly the one shown above and that your network allows HTTPS to llmrpm.com.

Notes

  • Amp speaks the Anthropic format, so it reaches LLMRPM through the proxy's model mappings.
  • Keep force-model-mappings on so every Amp model name resolves to a known LLMRPM ID.