plan2apiExplore the API
YOUR AI, CONNECTED

Your subscriptions.
One API.

Turn your Claude, Codex, and Kimi subscriptions into one API. Bring your credentials. Build with a single key.

Explore the API How it works

Encrypted credentials. A key that's yours.

Your existing subscriptions
A single API for your code
Auth encrypted at rest
A SHORT PATH TO BUILDING

From subscribed to shipping.

Bring your subscription.

Add your Claude, Codex, or Kimi credentials. Start with the tools you already use.

Get your API key.

Your credentials are encrypted. You receive the key that unlocks them when you make a request.

Build something good.

Call one API from your apps, scripts, and workflows. Your subscriptions do the rest.

MADE FOR YOUR CODE

Different subscriptions.
Same starting point.

Your side project. Your internal tools. Your next big thing. Put the AI you already use behind the code you want to write.

Pick a provider to explore the API shape.

​curl "$PLAN2API_BASE_URL/chat/completions" \  -H "Authorization: Bearer $PLAN2API_KEY" \  -H "Content-Type: application/json" \  -d '{    "model": "claude/<model>",    "messages": [{      "role": "user",      "content": "Build something good."​    }]  }'
claude/<model>API PREVIEW
DESIGNED AROUND YOUR KEY

Stored encrypted.
Unlocked by you.

Your subscription credentials are encrypted at rest. Your API key enables decryption when a request arrives, rather than storing the key alongside your credentials.

What does this protect against?

The design limits exposure from a database-only leak: encrypted credentials alone are not enough to unlock your subscriptions. A stolen API key or a compromised live server is a different risk.

You have the AI.
Now put it to work.

Explore the API