VeriticityDocs
Dashboard

Building with AI

Give a coding assistant the Veriticity docs: llms.txt, llms-full.txt, every page as Markdown, the OpenAPI document and the copy-page menu.

A coding assistant writes a better Veriticity integration when it reads these docs rather than guessing from what it was trained on. Every page is published as plain Markdown as well as HTML, with an index at /llms.txt in the format most AI tools look for.

Docs for your assistant#

AddressWhat it holds
/llms.txtAn index: what Veriticity is, rules for building with it, and a link to every page’s Markdown. Start here.
/llms-full.txtEvery page in one Markdown file, in reading order.
/quickstart.mdAny page as Markdown: add .md to its address. The introduction is /index.md.
/openapi.jsonThe OpenAPI document: every endpoint, parameter, schema and error code.

They are made from these pages each time the docs are published, so they always say what the pages say.

Giving your assistant the docs#

Most coding assistants can read a web address you give them. Point yours at the index, or at the one page you are working from:

Prompt
Read https://docs.veriticity.com/llms.txt and follow its instructions for coding assistants. Then help me submit a purchase to Veriticity from my server, using the Sandbox.

Where your editor keeps documentation sources, add https://docs.veriticity.com/llms-full.txt as one, so the whole docs are available without fetching page by page.

The copy-page menu#

Every page has a Copy page button beside its breadcrumbs:

  • Copy page copies the page as Markdown, ready to paste into a chat.
  • View as Markdown opens the page’s .md address.
  • Open in Claude and Open in ChatGPT start a chat that reads the page, so you can ask questions about it.

What llms.txt tells an assistant#

Besides the links, /llms.txt gives an assistant these rules. Each restates something these pages already say.

  • Build and test against Sandbox: https://sandbox.veriticity.com with a cmp_test_ key. Live is https://app.veriticity.com with a cmp_live_ key.
  • Keep API keys on the server. A key's secret is shown once and only a hash is stored.
  • Nothing is allowed until a policy allows it. An agent with no applicable policy gets NO_APPLICABLE_POLICY.
  • Check before you buy: a simulation runs the same evaluation as a purchase and changes nothing.
  • Send an Idempotency-Key on every purchase request. It is required, and makes a retry safe.
  • Identify the merchant by its website, merchantDomain. A merchant name identifies no merchant.
  • APPROVED is permission for that one purchase on exactly its terms, until expiresAt. It is not a purchase and not a payment.
  • REQUIRES_APPROVAL means a person decides. Wait for the decision; never treat it as approved.
  • A decision is final. Do not resubmit a refused purchase with altered details to get a different answer.

Agents that make purchases#

This page is about an assistant helping you build. An AI agent that makes purchases through Veriticity is a different case: it connects to the MCP server or calls the API with its own key, and its rules are the assistant instructions.

Keep secrets out of prompts#

Never paste an API key, a webhook signing secret or an execution token into a chat. Use a cmp_test_ key in Sandbox while you build, and keep keys in your server’s environment. The Markdown docs hold no secrets and no account details.