Surveymatic

For developers & agents

Machine-legible surveys, on purpose

Surveymatic is built to be used by software, not just clicked by humans. Create surveys, collect responses with AI follow-up probing, and read per-response confidence scores — all programmatically, with a human in the loop where it matters.

What the API offers

REST API with OpenAPI 3.1

The same API the app itself uses, documented by a generated OpenAPI 3.1 spec. Read the human-friendly reference, download the machine-readable document, and generate a client in minutes.

API docsOpenAPI JSON

Scoped API keys

Issue per-workspace keys with exactly the scopes an integration needs — surveys:read, surveys:write, responses:read. Keys are hashed at rest, shown once, expire after a year by default, and rate-limit at 60 requests per minute. Billing stays human-only, always.

MCP server, Streamable HTTP

Point any MCP client at one endpoint with the same API key — no second credential, no OAuth dance. Four tools: create_survey, get_results, list_surveys, stop_survey. Agents draft surveys and read confidence-scored results; publishing stays a human decision.

Agent discovery built in

An A2A agent card lives at /.well-known/agent-card.json, so evaluators and orchestrators can find the API, understand its skills, and verify claims programmatically instead of taking marketing copy on faith.

agent-card.json

Agents draft. Humans publish.

Every survey an agent creates starts as a draft, and API keys are technically unable to publish one — launching a survey requires a signed-in human in the app. That is deliberate: publishing spends your AI follow-up budget, and budget decisions belong to people. Agent usage meters against the same workspace pool, so there is one bill and no surprises.

Get started in three steps

  1. 1

    Create a scoped key

    Sign in, open the API page in your account menu, and issue a key with just the scopes you need. It is shown once — store it somewhere safe.

  2. 2

    Read the docs

    The reference covers every endpoint, the scopes each one requires, and the four MCP tools. The OpenAPI document is generated from the same schemas that validate requests, so it cannot drift.

  3. 3

    Connect your agent

    Use the key as a Bearer token against the REST API, or point an MCP client at /api/mcp. Surveys your agent creates land as drafts; you review and publish from the app.

Put your agent to work

Free plan, no credit card. Issue a scoped key and have your agent draft its first survey today.