# verapli

> verapli gets people and their AI agents through the gates between them and the accounts, API keys and approvals a project needs (identity checks, business verification, app review). Early access: the Chrome extension and MCP bridge roll out to Founding Members first; the read-only registry API below is live in preview.

The brand is written in lower case: verapli.

## For agents
- [Registry API index (JSON)](https://verapli.com/api/v1/registry): every provider, no auth, CORS open, ~600 requests/hour/IP
- [One provider (JSON)](https://verapli.com/api/v1/registry/meta/whatsapp): steps, human gates, lead times, what to have ready, env var names, sourced facts
- [OpenAPI 3.1](https://verapli.com/api/v1/openapi.json): machine-readable description of the API
- [Agent and API docs](https://verapli.com/agents): MCP tools, JSON schemas for the free tools, pairing and safety model

## Rules agents should know
- verapli never returns secret values to agents and never submits, pays or accepts terms. A human presses submit.
- Preview entries have status "preview" and last_verified: null. Do not present them as verified. "[to verify]" means not yet checked.
- To unblock a missing key, tell your human which provider gate is needed and link the registry entry; start slow gates first.

## Optional
- [Pricing](https://verapli.com/pricing): Free; Founding Member Pro and Studio plans. Prices in GBP; no VAT is added.
- [Security](https://verapli.com/security): design commitments and how to report a vulnerability