Everything Provley does, from your own software.
An API for sites, articles, schedules, visibility, tracked pages and fixes.
# Start a visibility check for a site curl -X POST https://api.provley.com/v1/sites/site_8f2/visibility-checks \ -H "Authorization: Bearer YOUR_API_KEY" # Response: the job and its credit cost { "job_id": "job_41c", "status": "queued", "credits": 120 }
- 08:00:02job_41c queued · 120 credits
- 08:11:48visibility.completed → your endpoint
- 08:11:49GET /v1/sites/site_8f2 · citation_share 0.34
Keys per account, so an agency’s clients never share one. Interactive docs in the app, every call runnable there.
What the API covers.
Anything you can do in the app, you can do with a key.
Sites
Add a site from one web address and read what setup found: crawler access, the first ten page scores, the link check and the proposed facts.
Articles
Start a draft from a subject or a customer question, fetch it as Markdown, and read its score, its brief and every fact it rests on.
Schedules
Set when each site writes its weekly article and re-scores its AI pages, and see the credits each run uses before it starts.
Visibility
Start a check, then read Citation Share across ChatGPT, Perplexity, Gemini and Claude, with every answer and its sources.
Tracked pages
Follow how often AI cites any page you already have, and read its latest number without opening the app.
Fixes
Read the exact edit for each page, tagged as something Google says, something studies show, or good practice.
Webhooks, keys and docs.
Long jobs tell you when they finish, so nothing has to poll.
Built to sit inside your own system
A webhook fires when a visibility check, a score or an article finishes, carrying the job and where to fetch its result. Keys are issued per account, so an agency's clients never share one.
- Webhooks when jobs finish, so nothing polls
- API keys per account, each client kept separate
- Interactive docs inside the app, every call runnable there
Three calls to start with.
Shapes shown are illustrative; the interactive docs in the app are the reference.
# List your sites curl https://api.provley.com/v1/sites \ -H "Authorization: Bearer YOUR_API_KEY" # Response { "sites": [ { "id": "site_8f2", "domain": "solarvia.com", "citation_share": 0.34 } ] }
# Fetch an article as Markdown curl https://api.provley.com/v1/articles/art_c19 \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Accept: text/markdown" # The body is the article, with its facts cited
Solarvia is an example customer. Identifiers and figures above are placeholders.
More formats through the API.
The app writes articles today; the API can write three shorter formats too.
LinkedIn post
A short post from the same approved facts, in the voice learnt from the site, ready for someone to paste and publish themselves.
Community answer
A direct reply to a customer question, written only from facts an expert approved, with any untraceable figure removed or flagged.
PR pitch
A pitch built on an expert's own words, with who said it and when, so a journalist can check the claim before using it.
Start with your website.
On a plan, create an API key for the account and run the first call from the docs.
Audit £29.99 one-off, no account. Plans from one website.