Give your agent hands.
Connect Orisu to Claude or ChatGPT and your assistant builds and runs real creative workflows, with the canvas loading right in the chat. Your own services call the same apps over the API.
One connection. Every model.
Your assistant or your backend talks to Orisu. Orisu picks the right model for each step, from video to voice, and keeps it all in your brand.
Claude
ChatGPT
- { }Any MCP client
Your store
Say it. It happens.
Thirty-plus tools sit behind plain requests. When something fails, the error says what to do next, so the assistant fixes it on its own.
- “Build me a workflow for launch ads.”
create_agentThe canvas appears in the chat.
- “Run it on the soda, in our brand.”
get_brand_contextrun_workflowPriced, run, and the ads come back.
- “Make the third one warmer.”
update_node_configtrigger_node_runOnly that step runs again.
- “Turn this into an app for the team.”
publish_appA form your teammates can run.
- “Now do it for all 248 products.”
create_feedrun_feed_columnOne row per product, all of them running.
- “What will that cost before I say yes?”
estimate_run_costA number, before anything spends.
Connected in two minutes.
No code for the chat route. Sign in once and every conversation can reach your workflows, your brand and your apps.
- 1Add the connector
Add custom connectorRemote MCP server URLhttps://api.orisu.ai/mcpAdd
Paste the endpoint into Claude or ChatGPT as a custom connector.
- 2Sign in and pick a workspaceOrisu would like to✓Read your workflows✓Run workflows and apps✓Read your brandAllow
Approve what it may do. It works in that workspace and nothing else.
- 3Ask for the workRun Spring launch on the soda



The canvas and the results show up in the conversation.
Your services, too.
Deploy a workflow as an app and it becomes an endpoint. Post the inputs, poll the run, read the outputs. The same app your team runs from a form.
POST /v1/apps/:id/runswith the photo URLYour app runsin your brand


curl -X POST https://api.orisu.ai/v1/apps/$APP_ID/runs \
-H "Authorization: Bearer $ORISU_KEY" \
-H "Content-Type: application/json" \
-d '{"inputs": {"product_photo": "https://shop.example/soda.jpg"}}'
# { "data": { "runId": "run_…", "status": "queued" } }
curl https://api.orisu.ai/v1/apps/$APP_ID/runs/$RUN_ID \
-H "Authorization: Bearer $ORISU_KEY"Organization keys with scopes you choose. Files by URL up to 100 MB. Outputs keyed by node. Server to server only.
Read the docs ↗This page reads like markdown too.
Switch to Agent view for the same facts as plain markdown, or send your agent to /product/api.md. No scraping, no guessing.
Before you connect.
Which assistants can use Orisu?
Claude, ChatGPT and any client that speaks MCP. Paste the endpoint into the connector settings and sign in.
Does the assistant spend credits without asking?
Every run is priced before it starts. Tools accept a spending limit, and the assistant can ask you before going over a threshold you set.
Can the assistant break my workflows?
Edits are checked against the latest version, so a stale change fails instead of overwriting someone else's work, and every save is versioned so you can restore it.
How do API keys work?
Owners and admins create organization keys in Settings. Each key carries only the scopes you give it, and you revoke it to rotate.
Can I call the API from the browser?
No. API keys aren't browser-safe, so the API is server to server. Call it from your backend, a worker or a script.
Let it do the work.
Free plan, 100 credits a month, no credit card. Connect your assistant in two minutes.