From OpenAPI
Bring one useful API call into your AI.
Start with a question your team already asks every week: where is this order, which tickets are open, what does this customer have. Studio turns that one operation from your OpenAPI spec into an app your AI can call.
Early access. Importing and editing are free until 1 January 2027. Model tests use workspace balance; app-tool charges are separate. Apps stay private to you, shared with your workspace, or public on Launch.
Pick the first read
What a useful first read looks like
A spec describes everything a service can do. Your first app needs one thing it does well. Pick a read you would recognise as right the moment you see the answer.
A good first read
- Reads, it does not change anything. Writes can come later, behind a confirm.
- Answers a question someone asks every week.
- Returns something you can check by eye: an order status, a ticket list, one customer record.
- Runs on an account you already own, with a key you can set up yourself.
Leave for later
- Every endpoint in the spec at once.
- Deletes, payments and anything you cannot undo.
- Calls into someone else's account. A spec never grants that access.
- Exports so large nobody would read them in a chat.
Examples, for illustration: “Find the status of order 4471”, “Show open tickets assigned to me”, “Look up the customer with this email”.
Five steps
From spec to answer
Open Studio and paste your spec
Paste an OpenAPI spec, or the URL of an MCP server you already run. Studio lists its operations.
Pick one read and its card
Choose the operation and a card for its answer: list, detail, table or status, and the fields it shows.
Set up the key in Studio
Add the key the API needs in the setup step. It is sealed in the vault and added on our side. Never paste it into a chat, a public spec or a screenshot.
Preview, then activate
Check the card drawn from a sample response, then activate. The app answers at its own address and through your ahel connector.
Ask your AI
Connect ahel to your AI once, then ask the question you picked. Claude shows the card; Cursor, Claude Code and Codex get the text version.
Connecting your AI for the first time? Connect Claude, or pick another AI on Setup.
The boundary
What the spec does, and what it does not
Studio does
- Read your OpenAPI spec or MCP server and list its operations.
- Give each operation a card and a text version of that card.
- Serve the app at its own MCP address and through your ahel connector.
- Keep the key in the vault, never in the conversation.
It does not
- Grant access your account does not already have.
- Make every endpoint a good tool. You choose which ones.
- Submit your app to the Claude or ChatGPT directory. You do that yourself, with the kit Studio prepares.
- Move an existing Custom GPT's credentials or sharing for you.
For a team
Decide who owns it before you share it
Saving a draft is not the same as giving it to your team. Before you share an app, decide three things.
Who owns the vendor connection
One key in the vault serves the app. Pick the person or service account it belongs to.
Who can use it
Keep it private, share it with your workspace after the owner or a team lead approves that version, or make it public on Launch or Team.
Who maintains it
APIs change. Someone has to update the app when the spec does.
Try Team for 14 days with no credit card. Your existing Free allowance applies during the trial, and it returns to Free on its own with nothing charged. Team adds the shared vault, approval rules and the audit log. See plans.
Questions
Before you start.
Do I need to write an MCP server?
No. Paste an OpenAPI spec and Studio serves the app as an MCP server at its own address. If you already run an MCP server, you can paste its URL instead.
I have a Custom GPT with Actions. Can I reuse its schema?
An Action is described by an OpenAPI schema, the same kind of document Studio reads. Credentials and sharing do not move over by themselves: you set up the key again in Studio and choose who gets the app.
Which AI shows the cards?
Claude shows the cards. Cursor, Claude Code and Codex get the complete text version. ChatGPT works through Developer mode; cards there are not verified yet.
Can my AI change data through the app?
Start with reads. When you add an operation that changes something, ahel asks you to confirm before it runs.
What does it cost?
Early access. Importing and editing are free until 1 January 2027. Model tests use workspace balance; app-tool charges are separate. Apps stay private to you, shared with your workspace, or public on Launch. Current plan prices are on the pricing page.
Start with one read.
Paste your spec, pick the question your team asks most, and ask it from your AI.