Three routes, one workspace
Use Chat Completions, Responses, or Anthropic Messages without translating one request format into another.
See the request formats THE API LAYER FOR YOUR NEXT IDEA
Build with AI.
Stay in flow.
Chat Completions, Responses and Anthropic Messages—each in its native request shape, with one private workspace for keys and usage.
MOCK MODEL ACCESS NO LIVE MODEL ACCESS
POST
NATIVE ROUTE
OpenAI chat schema/v1/chat/completionsREQUEST EXAMPLEcURL
: "${OPENMAGIC_BASE_URL:?Set gateway origin}"
: "${OPENMAGIC_API_KEY:?Set API key}"
curl \
"$OPENMAGIC_BASE_URL/v1/chat/completions" \
-H "Authorization: Bearer $OPENMAGIC_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "relayforge/atlas-chat",
"messages": [{"role": "user", "content": "Hello"}]
}'Set OPENMAGIC_BASE_URL first · messages array · role and content
A calmer route from prompt to product.
Three native protocolsClear model IDsUsage visibilityKeys you control
A BETTER DEVELOPER LOOP
Less glue code.
More room to make.
Bring model access, keys, and usage into one workspace with a predictable API surface.
Keys with a clear boundary
Create a key, copy it once, and revoke it when you no longer need it. Secret values are never listed again.
Manage API keysKnow what your app is doing
See request and estimated token activity together in one developer console. Cost stays unavailable until verified model rates are configured.
View account usageA MODEL CATALOG THAT STAYS HONEST
Choose by the work
in front of you.
Browse a small sample catalog by general, reasoning, and coding workflows. This local preview uses mock IDs; real provider availability and rates are not configured.
Sign in to your workspace catalogMODELWORKFLOWCONTEXTRATE
relayforge/atlas-chatGeneral128KNot published
relayforge/atlas-reasonReasoning64KNot published
relayforge/atlas-codeCode128KNot published
Demo IDs only. Live models and pricing are not available in this preview.
MADE FOR BUILDERS
Familiar in the first
five minutes.
Choose Chat Completions, Responses, or Anthropic Messages. Keep your provider credential on the server and configure a live adapter only when permitted.
Open API reference01
Keep your current client
Use the matching request shape and OpenMagic API key for each protocol.
02
Start with a workspace key
The private console stores only key digests and lets you revoke access.
03
Connect only with permission
A live adapter needs a provider agreement that allows third-party proxying.
YOUR NEXT BUILD STARTS HERE
Make the first request
feel easy.
Sign in with a one-time email code to manage your workspace. Payments and live model access remain disabled.
Create your workspace LOCAL DEMO · MOCK RESPONSES · NO CHARGES