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, and new RSS items — Amistio registers the webhooks and verifies the deliveries for you.
• 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; read-only tools run on their own, every other tool waits for your approval.

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 Integrations in the Builder to connect your accounts and add MCP tools; anything not available yet is honestly marked coming soon. Only connect MCP servers you trust — their output is treated as data, never as instructions.

Find it from inside the app

Inside Amistio there are two sides, Use and Build — and developers are builders. From the Use side, press Build agents at the bottom of the left column to reach the Builder; then open Integrations 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 every left column, also offers Help & guides, which brings you back to these guides. There is no third developer side to look for.

Believe the boundary

Amistio does not offer a public REST API, public API keys, an SDK, a CLI, or an extension marketplace today. If you need those, tell us — that need is feedback, not something to hunt for in the product.

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