Free
£0 for ever
Read every guide, plan a project and let any agent query the registry.
Join freeEarly access · Founding Members open
Get through every gate.
The accounts, API keys and approvals your project needs — for you and for the AI agents building it — in about an hour. verapli knows the order, the paperwork and the traps. You stay in charge and press submit.
Early access. The Chrome extension and agent bridge roll out to Founding Members first; the public registry API is live today in preview.
- OPENAI_API_KEYwritten
- SUPABASE_URLwritten
- STRIPE_SECRET_KEYwritten
- GOOGLE_CLIENT_SECRETin review
- TWILIO_MESSAGING_SERVICE_SIDin review
- WHATSAPP_TOKENin review
The problem
Code is cheap now. Accounts aren’t.
Your agent writes the WhatsApp integration in ten minutes, then stops at a blank line: WHATSAPP_TOKEN=. It can’t fill it. Only you can — and getting it can mean identity checks, business verification and a review by a person at the provider. The agent stops, the context is lost, and the project waits.
When we needed a WhatsApp number for one of our own products, the chain was: a personal Facebook account, then a Business Portfolio, then Business Verification, then a developer app, then display-name approval (rejected twice), then a system user and a permanent token. Nineteen working days. About three hours of actual work. The rest was waiting, guessing and resubmitting.
A checklist can’t make a provider’s queue shorter. It can stop you joining the back of it again after an avoidable rejection — and that’s where most of the weeks go.
Meta Business Verification
Meta doesn’t publish a turnaround we could verify. On Meta’s own developer forums, people report reviews stuck for months, and one reply calls a 10-day wait “not unusual anymore”.
Google restricted scopes
OAuth verification plus an annual CASA security assessment: 2–3 weeks (tier 2) or 4–6 weeks (tier 3), with assessor fees of $500–$4,500, according to Google.
Twilio A2P 10DLC
Campaigns are rejected if the website is only a form (error 30920) or doesn’t show enough about the business and how people opt in (error 30919). Both are checkable before you submit.
Sources checked October 2026. More in the registry preview.
How it works
One guided path, about an hour of your time
A Chrome extension that works alongside you on the providers’ own websites, plus a bridge so your coding agent can ask for what it needs. Pause and resume at any step.
Interview
Tell us what you’re building, or let your agent answer from your repo. We work out which providers and keys you need.
Get ready
A checklist of what providers will ask for: ID, company documents, a live website, a domain email. Checked before you queue.
The guided hour
Slow gates first, so the waiting starts today. In your browser, fields are filled and the next button is highlighted. You press submit.
Keys into .env
Captured from the provider’s page by plain code, encrypted in your browser, written to .env.local. No copy, no paste.
Watch
Pending reviews, chase dates and renewals in one place. If something is rejected, you see the likely reason first.
Built for agents
Your agent asks. You press submit.
Built for MCP-capable coding agents such as Claude Code, Cursor, Codex and Goose. Your agent can look up what any provider needs, plan the whole project, start the slow gates early and keep building with mocks. When the key lands in .env.local, it’s told the key is there — never what it is.
registry.search,requirements,plan— free for any agentstart_session,session.status,request_human— after you pair the agentkeys.statusreports present, missing or placeholder. No tool ever returns a secret.- No tool can submit, pay, accept terms or click. Agents ask; you decide.
Claude Code
# Early access: Founding Members receive the bridge first
claude mcp add verapli -- npx -y verapli mcp
# Then, in your agent:
> "What do I need for WhatsApp, and how long will it take?"Public registry API · live now (preview)
curl https://verapli.com/api/v1/registry/meta/whatsappTrust
Designed so we can’t see your keys
A tool that sits between you and your most important accounts has to earn trust in its design, not its marketing. These are the commitments the early-access extension and agent bridge are built and tested against. We’ll publish independent review results when we have them.
Providers
Launching with the hardest gates first
The slow, rule-heavy gates are where projects lose weeks, and they’re the ones nobody else covers. We start there, then add the easy ones.
- Meta & WhatsApp
- Google OAuth verification
- Apple Developer (organisation)
- Google Play (organisation)
- Twilio A2P 10DLC
- OpenAI
- Anthropic
- Stripe activation
- Microsoft Entra
- Slack
- PayPal
- AWS & SES production
- Supabase
- Resend
- Upstash
- Vercel
- Neon
- Clerk
- PostHog
- Cloudflare
- …and more
Target for version 1.0: around 150 providers. An entry is published only after a person has checked it against the provider’s current rules and dated it. Provider names are used only to describe what verapli helps with; we’re not affiliated with them.
Pricing
Free to start. Founding prices for early backers.
Founding Members get early access as it rolls out, keep their founding price for as long as they stay subscribed, and can have a full refund at any time before general availability.
Pro
Founding price£12 per month
or £99 per year
For founders and developers shipping more than one project.
Studio
Founding price£39 per month · 5 seats
extra seats £6/month each
For studios and agencies setting up providers for clients.
Become a Founding StudioProject Pass
Available at public launch£19 one-off, per project
Everything one project needs, without a subscription.
Join the Project Pass listQuestions
Can I use verapli today?
Partly. The public registry API is live in preview. The Chrome extension and the agent bridge are in early access and roll out to Founding Members first, in waves. Everyone on the free list hears from us when it opens for them.
What does a Founding Member get?
Early access as it rolls out, your founding price locked for as long as you stay subscribed, a direct line to us to shape which providers come next, and a no-quibble full refund at any time before general availability. Founding terms.
Can you guarantee my verification gets approved?
No, and nobody honest can: the provider decides. Our job is to make sure you submit the right thing the first time, start slow queues early, and know what to do if something comes back.
Do you see my API keys or documents?
No. Keys are captured and encrypted in your browser and written to your own files. Documents go straight from you to the provider. Our servers hold your email, your plan and a hash of your licence key — that’s it. Details.
Could using verapli get my accounts flagged?
verapli doesn’t automate signups, solve CAPTCHAs or submit anything. You do every submission yourself, in your own browser, on the provider’s own site, with the relevant rules in front of you.
Which browsers and agents?
Chrome and Microsoft Edge on desktop at launch. For agents: anything that can use a local MCP server (such as Claude Code, Cursor, Codex and Goose), and anything that can make an HTTP request for the public registry.
Is this legal advice?
No. Terms notes are plain-English summaries with links to the source and a date. For regulated questions, speak to a qualified adviser.
Who is behind verapli?
verapli is made by VOCABOTICS LTD, a UK company. We built it after losing weeks to these gates on our own products. Say hello at hello@verapli.com.
Start the slow gates sooner
Join free and we’ll email you when early access opens for you. Or back us now as a Founding Member.