Stripe on Orkestia

Orkestia is the backbone that connects software, AI, and the real world. Stripe is how money moves for a lot of the software on that backbone, including Orkestia's own published plan. This post is the connection: store the account once, then treat customers and invoices as workflows you start from the console, the API, or an agent.

Connect the account

Add a Stripe connection in the console after you create an account. The secret key stays encrypted on the connection. It does not go in chat, in Staff env, or in initial_data. An agent that starts a Stripe-typed workflow uses the connection. It does not hold the key.

Browse live types in the catalog. If the schema has has_prerequisites: true, the prerequisite is almost always this connection. Call get_workflow_prerequisites from MCP and follow the guide.

The plan you subscribe to

The open plan on pricing is Stripe billing the console already uses. A user seat is a person. A key seat is an agent or an integration key. There is one published plan and every customer pays the same rates. Subscribe from app.orkestia.dev/start. How seats work is in Billing and seats.

That is Orkestia charging you. It is a different object from a Stripe connection you add so your customers and invoices can be workflows. Keep the two straight.

Stripe and Omie

When the books live in Omie, Stripe stays the source for the customer and Omie stays the ledger. The code you send Omie is the Stripe customer id, not the email address. Email can sit on the cadastro. It is not the join. Walkthrough: Omie on Orkestia.

From MCP

whoami()
list_workflow_types(prefix="stripe.")
get_workflow_schema("<type>")
start_workflow(workflow_type="<type>", initial_data={...})
watch_workflow(workflow_id)

Start with a read-only type. Read the payload, not only the status.

What a first afternoon looks like

1. Subscribe so the org exists. That is Orkestia charging you, on pricing.
2. Add a Stripe connection with a restricted key if Stripe lets you scope it. Test the connection.
3. From MCP, list_workflow_types(prefix="stripe."). Open one read-only schema. Start it. Read the customers or invoices in the run payload.
4. Only then a write, and only after get_workflow_schema.

If you also keep books in Omie, do not join the two on email. Send Omie the Stripe customer id as the declared integration code. Omie on Orkestia.

Do not put the Stripe secret in a Staff skill file. Staff actors use the connection the same way Claude does.

What to read next

• The catalog
• Pricing
• Documentation

hello@orkestia.dev if the connection test fails.