Studio quickstart

In this tutorial you make an app from your own product in Studio and use it from your AI. Start small: one thing people already ask for, such as finding an order or checking a project's status. A narrow first app is easier to check than a whole system at once.

#What you need

• An ahel workspace where you are the owner or a team lead, with an AI tool connected. If not, start with Connect Claude.
• One of these:
  • your product's website, if it publishes an API description,
  • an OpenAPI 3 document (JSON or YAML) for your API,
  • the address of an MCP server you run, over HTTPS.
• A key for the API, if it needs one. Use a key with only the access the app should have.

An API description says what a service can do. It does not give anyone access: the key you add decides what the app can reach.

#1. Tell Studio which product

Open Studio and start a new app. The first step is Which product?

• Paste your website or API address and press Find it. Studio looks for an API description. If it finds one, it imports it. If it can only read your docs, it drafts the actions and marks them "Drafted from docs, check each".
• If you have the document or a server, open Advanced (for developers):
  • OpenAPI document: paste the document and press Read document.
  • MCP server: enter the server's https address, and the header name and key type if it needs a key, then press Read tools.

If Studio says "No API found on this site yet", it needs an API document or an MCP server. If it cannot read your source, it offers Copy a message for your developer, with what to send them.

#2. Choose what it can do

The next step is What can people ask it to do? Studio sorts the actions into three groups:

Tick the one or two lookups your first users need, and leave the rest for later. Changes and deletes start unticked.

If the API needs a key, Studio asks for it here: "This product needs a key. Paste it once; your AI never sees it." The key goes into your workspace's vault.

#3. Test it

In Test it, run the lookup you picked and check the answer and the card it makes. If the answer is wrong or empty, go back and check the key's access or pick a different action. Test an app before you share it covers the try page and tester links.

#4. Put it in your AI

The last step, Put it in your AI, shows how to reach the app. Because your AI already has ahel, the app is there: start a new chat and ask for the thing you built it for, such as "Using ahel, find order 1042."

You should see the answer, as a card in Claude or as text elsewhere. Changes still show a confirm card first.

The app is private to your workspace. Nobody outside it can use it until you publish it.

#Limits to know

• A document can be up to 2 MB, and Studio reads the first 200 operations. Trim larger documents to what the app needs.
• Keys: an API key in a header or the query, basic auth, a bearer token, or OAuth sent as a bearer token. An API whose first security scheme cannot be sent this way is refused, with that reason.
• Request bodies must be JSON, and the document needs one complete HTTPS server address.
• Public and signed-in operations go in separate apps.

#Next

• Test an app before you share it.
• Publish an app.