AMP Provider

AMP is a managed Anthropic pipeline that adds resilience and optimization layers on top of Claude models. Rensei integrates with AMP for cost-optimized, high-throughput deployments.

Provider Summary

Attribute	Value
Provider ID	`amp`
Display name	Amp
Config namespace	`anthropic` (shares config with Anthropic)
Supported auth modes	`byok`, `metered`
Requires endpoint	No
Category	Managed

A model profile may include either or both modes in its auth_modes array. The resolver prefers byok over metered. If the org or project access policy excludes byok, metered is used automatically. See Auth Modes for the resolution algorithm.

When to Use AMP

Use AMP when you want:

Cost optimization - Automatic request batching and smart routing.
High throughput - Designed for batch and streaming workflows.
Reliability - Built-in fallback and retry logic.
No endpoint management - AMP is fully managed; you provide a token.

For interactive, real-time work, prefer direct Anthropic integration.

Available Models

AMP proxies Anthropic Claude models:

Claude Opus 4.1 - High reasoning capability via AMP pipeline.
Claude Sonnet 4 - Balanced speed/quality via AMP pipeline.
Claude Haiku - Fast inference via AMP pipeline.

Check rensei catalog list --provider amp to see current models.

Auth Modes

BYOK

Bring your own AMP token:

Get an AMP token from your AMP account dashboard.
In Settings → Integrations, click Add Provider and select AMP.
Paste your AMP token and click Test Connection.
In Settings → Model Profiles, create a profile with auth mode byok and select an AMP model.

Your org is billed directly by AMP for token consumption.

Metered

Platform supplies a managed AMP token. Your org is billed through Rensei's cost ledger. Metered mode must be enabled for your organization by the platform operator - see Auth Modes for details.

Setup (user):

In Settings → Model Profiles, create a profile with auth mode metered and an AMP model.
Dispatch runs if your org is entitled; contact Rensei support to enable metered mode.

Configuration

AMP shares the anthropic config namespace with direct Anthropic integration. You can override context window and other Anthropic-native parameters:

{
  "providerConfig": {
    "anthropic": {
      "contextWindow": 100000,
      "cacheControl": true
    }
  }
}

Example Profile: Batch Processing via AMP

rensei profile create \
  --name "amp-batch-processing" \
  --provider amp \
  --model-id "claude-opus-4-1" \
  --auth-mode metered \
  --scope org \
  --org-id my-org

Then route all batch research work through AMP:

rensei routing set \
  --scope org \
  --org-id my-org \
  --work-type research \
  --profile-id prof_amp_batch_processing

Pricing

AMP pricing is typically 5-15% cheaper than direct Anthropic for batch/streaming work due to optimization and request batching. View pricing:

rensei catalog show claude-opus-4-1-amp --format json | jq .pricing

For metered mode, cost events emit automatically with the org ID for billing.

Troubleshooting

"No metered key is configured for provider 'amp'"

The platform's metered key pool for AMP is not configured. Contact your Rensei operator - deployment-level key pool setup is covered in the operator docs.

"Invalid AMP token"

Your BYOK token is expired or malformed. Regenerate it from your AMP account dashboard and update Settings → Integrations.

Model not found in catalog

Add it to your catalog:

rensei catalog create \
  --provider amp \
  --model-id "claude-opus-4-1" \
  --display-name "Claude Opus 4.1 (via AMP)"