Trazo for agents
Nearly everything Trazo does, an AI agent can do too. Integrating a contact form, provisioning sites, reviewing submissions, inviting users: all of it goes through one JSON API, and the whole reference fits in a single markdown file an agent can fetch and read.
Built to be driven by agents
There are two kinds of keys. A site key (sk_live_…) lets an agent wire a contact form to the public intake endpoint with one JSON POST and no SDK. A personal key (trz_pat_…), created on your account page, lets it manage organizations, sites, submissions, and users with exactly your permissions.
There is nothing agent-specific to enable: the management API is the same one the dashboard uses, responses are plain JSON with a stable English contract, and errors follow one predictable shape.
The machine-readable reference
The complete reference (both APIs, authentication, envelopes, error codes, role rules, every endpoint) lives in one markdown document at https://gettrazo.app/docs/trazo.md. Point an agent at that URL instead of pasting docs into a prompt.
curl https://gettrazo.app/docs/trazo.md
Agent bootstrap prompt
Paste this into your agent to get it started. It tells the agent where the reference lives and which key does what:
You are integrating Trazo (https://gettrazo.app), a contact-form backend with spam filtering. Fetch and read https://gettrazo.app/docs/trazo.md for the complete API reference. To submit forms you need a site API key (sk_live_...); to manage organizations, sites, submissions, and users use a personal API key (trz_pat_...) created at https://gettrazo.app/account, sent as 'Authorization: Bearer <key>'. All responses are JSON; errors follow {"error": {"code", "message", "details"}}.