Official agent entry point

One API for contact experiences built by humans or agents.

Create and publish Contact Button Pages, buttons, forms, bookings, callbacks, knowledge, chat, and workspace settings through the public v1 contract. This domain tells agents where to start, what they may do, and when a person must confirm.

Read the agent skill Open the API quickstart

Canonical surfaces

Start with a contract, not a guess.

The API hostname is JSON-only. This discovery hostname provides the human-readable map and direct links to every machine-readable interface.

REST API

Use https://api.contactbutton.com/v1 for all new integrations. Responses and errors are structured JSON.

Inspect the API root

OpenAPI specification

Use the live contract for operation IDs, parameters, request schemas, scopes, and typed responses.

Read the OpenAPI contract

Two MCP servers

Search public documentation at https://docs.contactbutton.com/mcp. Use https://api.contactbutton.com/mcp for authenticated product actions.

Read MCP setup

Portable agent skill

Load current setup steps, safety boundaries, confirmation rules, and secret-handling instructions.

Open SKILL.md

A first prompt

Start in your coding agent.

Use this with Codex, Claude Code, or another tool-capable agent. It points to live instructions instead of relying on remembered product behavior.

Set up Contact Button for me using the official instructions at:
https://agents.contactbutton.com/.well-known/agent-skills/contact-button/SKILL.md

First inspect my current workspace and make a plan. Read before writing,
keep stable resource IDs, and use idempotency keys. Ask before publishing,
buying a phone number, changing DNS, spending money, or taking another
externally visible action. Never ask me to paste secrets into chat.
After publishing, verify the HTML, Markdown, manifest, and agent metadata.

No guessing required

Discovery starts at predictable URLs.

This site is server-rendered, keyboard accessible, and useful without JavaScript. Agents can enter through a standard index, a portable skill, the OpenAPI contract, or a public profile manifest.

/llms.txtA short routing index for language models.
/agents.mdOperating rules, workflows, and product boundaries.
/.well-known/contact-button.jsonPlatform capabilities, publishing formats, actions, and safety rules.
/.well-known/api-catalogThe REST contract and protocol entry points.
/.well-known/agent-skills/…Portable setup instructions for coding agents.
/mcp.jsonDocumentation-search and product-action MCP metadata.
button.contact/name/manifest.jsonActions and public representations for one published Page.

Phone infrastructure

Telnyx is only required for phone and SMS.

Pages, buttons, forms, bookings, newsletter subscriptions, callback-request capture, and knowledge work without Telnyx. Connect a funded Telnyx account only for click-to-call, automated callback bridges, voice, call forwarding, or SMS. Keep the Telnyx API key outside model context and require human approval before purchasing a number.

Read the Telnyx setup guide

Stable by design

Existing integrations keep working.

The canonical address for new integrations is https://api.contactbutton.com/v1. The existing https://app.contactbutton.com/v1 alias remains supported so this discovery and hostname split does not break current users.

Agents should read the latest OpenAPI contract before writing, use least-privilege scopes, preserve stable resource IDs, and send a unique idempotency key with mutations.