REST when MCP
isn't enough.
Same 103-tool surface. Alternative protocol. For teams who need webhooks, programmatic auth, and a proper OpenAPI spec in their existing stack.
hello@carrier.llc · we'll notify you before early access opens.
MCP is the right interface when you're building AI agents. But not every integration lives inside an AI client. You have backends, lambdas, cron jobs, and CI pipelines that need to talk to the OCS directly — and they speak REST. Carrier API closes that gap.
The same fleet operations available through Carrier MCP are exposed as versioned HTTP endpoints with full OpenAPI documentation. Webhook subscriptions push OCS events to your infrastructure the moment they happen. Batch endpoints handle fleet-scale writes in a single call. Every write endpoint is idempotent.
The outcome is a unified control plane for your entire fleet — AI agents on one end, your existing backend on the other, and a consistent view of subscriber state across both.
What's coming
Same 103-tool surface
Every OCS operation available through MCP is available over REST. One model, two protocols.
Webhooks
Push events on subscriber state changes, package expiry, and usage thresholds to any HTTPS endpoint.
API key + OAuth
Static API keys for server-to-server. OAuth 2.1 for user-delegated flows. Per-key scope control.
Full OpenAPI spec
Machine-readable spec ships with every release. Generate SDKs in any language in minutes.
Idempotency keys
Safe retries on every write endpoint. No duplicate activations, no double charges.
Batch endpoints
Activate, assign, or query hundreds of ICCIDs in a single request. Built for fleet-scale operations.
Use cases
Custom integration layer
Your existing backend speaks REST, not MCP. Carrier API drops in as a standard HTTP dependency — no new toolchain, no model context, just endpoints.
Event-driven architecture
Webhook events feed directly into your data pipeline. Subscriber activations, package expirations, and low-balance alerts trigger downstream logic automatically.
Multi-language SDKs
Pull the OpenAPI spec and generate a typed client in Go, Python, Ruby, or whatever your stack runs. The spec is the contract.
CI/CD fleet testing
Automate ICCID lifecycle tests in your deployment pipeline. REST makes it trivial to script, assert, and tear down fleet state in CI.
Get early access
Carrier API opens to early access in Q3 2026. Drop your email and we'll reach out before the doors open.
Join the waitlist — hello@carrier.llc