Develop with Amistio: the shipped integration surfaces

By the end of this page you know exactly which ways of connecting your own software to Amistio exist right now — and which do not.

Start at the Developers page

amistio.com/developers lists every connection path that exists in the product today:

• Start agents from your systems: activate an agent with a webhook start; it mints a unique URL shown exactly once, and anything that can POST JSON to that URL can start the agent. Re-activating rotates the URL.
• Managed event triggers for Telegram messages, GitHub issues and pull requests, new RSS items, new videos on a YouTube channel, and new YouTube comments — Amistio registers the Telegram and GitHub webhooks and verifies the deliveries for you, and checks RSS feeds and YouTube every five minutes.
• Call Amistio from your own software: create API keys under Settings in your account menu — each is shown exactly once — then use /api/v1 to list your agents, start a run of an agent's published version with an Idempotency-Key, and read runs. Register the exact origins that may embed a published agent's public run page, and a callback URL to receive signed result events when a run settles. The OpenAPI document lives at /api/v1/openapi.json.
• Call any API from an agent, with reviewed connectors and plain HTTP calls.
• Bring your own connector by importing a connector manifest — it imports for review and never executes until published.
• Teach agents reusable behavior with Skills.
• Remote MCP servers: connect one from the curated directory or any URL you paste — sign in with OAuth, paste a server token, or connect a public server with no sign-in. Its tools, resources, and prompts are pinned when you connect; read-only tools and bounded resource reads run on their own, every other tool waits for your approval, and you can import its prompts as Skill drafts to review. A server can never drive the model or ask you questions.

Inspect the connector surface

Browse amistio.com/connectors to see every reviewed connector — each operation, its inputs, and its safety rules.

Connect accounts and tools

Signed in, open Connected apps from the left column to connect your accounts, add MCP tools, and browse the tool catalog; anything not available yet is honestly marked coming soon. Only connect MCP servers you trust — their output is treated as data, never as instructions.

Open Connected apps

Find it from inside the app

Inside Amistio there is one menu for everyone — and developers are builders. Connected apps is one of the four places in the left column of every signed-in screen; open Connected apps and choose Developer guide in the page header: it opens the public Developers page at amistio.com/developers. Your account button, at the bottom of that column, also offers Help & guides, which brings you back to these guides. There is no separate developer side to look for.

Read the reference and the guides

amistio.com/developers/api is the API reference. It is built from the same source as the OpenAPI document, so it always matches: every operation with its method, path, scope, parameters, and request and response shapes; how to authenticate (your key goes in the Authorization header, never in the address); the scopes; the protection bounds (60 requests per minute per key, 10 run starts, 30 document writes, and 10 freezes per minute per owner); the Idempotency-Key rule; cursor paging; every error code; and a changelog. Each request is shown in eight languages — curl, JavaScript, Python, Go, PHP, Ruby, Java, and C# — and always reads your key from your own environment, never from a pasted value.

amistio.com/developers/integrate holds the integration guides: a quickstart; result callbacks, including how to verify the signature on every event with a tested helper and working code in the same eight languages; embedding a run page on a site you registered; a run's life from start to settle; and connecting your own MCP server — Amistio is the client, the server is yours. The language you pick is remembered in your browser and follows you across the reference, the guides, and the app.

Try it from inside Amistio

Signed in, your account menu — the button at the bottom of the left column — shows Developers while the API is on. Pick one of your agents to see its id, whether it is live, and exactly which inputs it expects; copy a ready-made request in any of the eight languages with that agent's real id filled in; see its recent API runs; and send real requests from the try-it console. The console uses only your signed-in browser session: reads run freely, changes ask you to confirm first, and it never asks for, shows, or stores an API key. You never paste a key into the browser.

Create an agent from your terminal

Agents are files too. With a key that carries the agents:write and agents:publish scopes, you can create an agent from a JSON document, check a document without saving it, read and replace an agent's draft, freeze a version, and put it live or take it off — all under /api/v1, with exactly the checks a save in the Studio gets. The document's JSON Schema is at /api/v1/schemas/agent.json, so your editor or your CI can check a file before you send it. The quickstart on amistio.com/developers walks the whole path in nine short steps: key, schema, file, check, create, change, freeze, go live, run.

Every change through the API goes behind the revision you read: a stale revision answers 409 with the current one and changes nothing, so two writers can never silently overwrite each other. A document the Studio would refuse is refused the same way, with the same findings, and nothing is saved. An agent created this way is an ordinary agent — it appears on My agents with its Edit door, and the Studio marks the revision Edited through the API. There is still no SDK and no CLI: every call is plain HTTP, shown in eight languages on the reference.

Believe the boundary

Amistio does not offer an SDK, a CLI, or an extension marketplace today. Call the API directly with any HTTP client. If you need an SDK or a CLI, tell us — that need is feedback, not something to hunt for in the product.

Credentials are only ever entered through the Connected apps flows, stored encrypted, and sent only to the service they belong to. No agent definition, prompt, or log carries them.