Building with AI

Hand a coding agent the entire API in one fetch, so what it writes matches what the API does.

Give your agent the whole API

Paste this into Claude Code, Codex, Cursor or anything else that can fetch a URL.

It is one request, and it needs no credentials.

Prompt

Read https://app.blueticked.com/llms-full.txt — it is the complete Blueticked messaging API reference (auth, endpoints, scopes, error codes, webhooks). Then help me integrate it. Use a test key from the environment; never hard-code one.

The documents

Both are public, plain text, and generated from the same source as this reference — so they cannot describe behaviour the API does not have.

llms-full.txthttps://app.blueticked.com/llms-full.txt

The entire contract in one fetch: auth, conventions, every endpoint, every scope, every error code, the webhook rules, and the mistakes that actually bite. Point an agent here.

llms.txthttps://app.blueticked.com/llms.txt

A short index in the llms.txt convention — what exists and where the detail lives. Cheap to read before deciding what else to fetch.

openapi.jsonhttps://app.blueticked.com/api/v1/openapi.json

OpenAPI 3.1. The authoritative machine-readable schema for every request and response; generate a client from it.

AGENTS.mdhttps://app.blueticked.com/agent-kit/AGENTS.md

Drop-in repository instructions for Codex and compatible coding agents. It defines discovery, test-key, idempotency, webhook, and live-approval rules.

CLAUDE.mdhttps://app.blueticked.com/agent-kit/CLAUDE.md

Drop-in Claude Code project instructions that use Blueticked's remote MCP resources and guided integration prompts.

SKILL.mdhttps://app.blueticked.com/agent-kit/SKILL.md

An installable Codex skill for implementing, testing, debugging, and auditing Blueticked integrations.

integration-recipes.mdhttps://app.blueticked.com/agent-kit/integration-recipes.md

Reference architectures for SMS OTP, transactional email, WhatsApp notifications, external events, and signed webhooks.

Why it stays true

Generated, not written: The same endpoint definitions that render these pages and the OpenAPI document produce the text an agent reads. An endpoint cannot exist in one and not the other.
Tested for completeness: Adding an endpoint, scope, error code or webhook event without it appearing in the agent document fails a test, so the two cannot drift apart quietly.
Sandboxed by default: The guidance tells an agent to build against a test key, which simulates the whole send lifecycle without reaching a recipient or spending credit.
No credentials in generated code: It also tells the agent to read the key from the environment and name the variable, rather than writing one into the source it produces.

Let it act, not just read

If your client speaks the Model Context Protocol, it can call the API as tools instead of writing HTTP by hand.

Connect the MCP server: register it, then approve the connection in the browser, choosing the businesses, the access profile, Test or Live, and an expiry. A client that cannot sign in uses an expiring key from Agent access instead. Nothing needs to be installed inside the project.