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

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.

There's no CLI for browsing the catalog - model listing is a UI/API surface. See current models in Settings → Model Profiles → New Profile (the model dropdown filters to the provider you pick), or ask your operator to check Admin → Model Catalog.

Auth Modes

BYOK

Bring your own AMP token:

1. Get an AMP token from your AMP account dashboard.
2. In Settings → Integrations, click Add Provider and select AMP.
3. Paste your AMP token and click Test Connection.
4. 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):

1. In Settings → Model Profiles, create a profile with auth mode metered and an AMP model.
2. 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

There's no CLI for creating profiles - do this in Settings → Model Profiles → New Profile:

1. Name: amp-batch-processing
2. Provider: Amp
3. Model: claude-opus-4-1
4. Auth mode: metered
5. Scope: Organization
6. Click Create.

Then route all batch research work through AMP. There's no CLI for this either - in Settings → Model Profiles → Work-Type Routing, select scope Organization, set the research work type's default to the amp-batch-processing profile, and click Save.

Pricing

AMP pricing is typically 5-15% cheaper than direct Anthropic for batch/streaming work due to optimization and request batching. There's no CLI for reading the catalog - view pricing for a model in the operator console at Admin → Model Catalog (open the entry to see its pricing object).

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

There's no CLI for this - your operator adds it in Admin → Model Catalog (New entry), or via a provider Bulk import. See Managing the Catalog.

Further Reading

• Auth Modes - Full auth mode reference
• Anthropic Provider - Direct Anthropic integration (for comparison)
• Model Catalog & Routing - Catalog management and work-type routing