Every endpoint in the catalog is below, grouped by category. Each links to a reference page generated from the published schema, so what you read is what the API actually accepts and returns — there is no hand-maintained copy to drift.
367 APIs across 29 categories, all behind one key, one host and one response shape.
What every endpoint has in common
Before the list, the parts that never change:
| Host | https://api.apiverve.com |
| Path | /v1/<endpoint> |
| Auth | x-api-key header — see authentication |
| Response | status / error / data — see response format |
| Errors | HTTP status plus a sentence — see error handling |
So the difference between any two endpoints is the path, the parameters and the shape of data.
Everything else you learn once.
Reading a reference page
Each page follows the same order, and each section answers a specific question:
- Overview — what it is for, and when it is the wrong tool.
- Endpoint — the call in curl, JavaScript, Python and PHP. All four are the same HTTP request, so pick whichever you read fastest.
- Parameters — name, type, required or optional, constraints, and accepted values where the set is fixed. Premium parameters are marked.
- Response — a real sample response, not a schema sketch.
- Response fields — every field with its dot-path, type, an example value and a description.
- Errors — what it rejects and why.
- Use cases — what people actually build with it.
Credit cost
Most endpoints cost one credit per call. The ones that do more work — rendering, OCR, inference, multi-source lookups — cost more, and their cost is shown on the card below and again at the top of their reference page.
Failed calls are not billed. A credit is taken only when a source actually answers, so a bad parameter, a rejected credential and a blocked call all cost nothing — the request never reaches the source that would charge for it.
The case that is billed and surprises people is a successful call that found nothing. A lookup returning an empty result did the work you asked for, and it costs its credit. An empty answer is an answer — see errors.
Your remaining balance comes back on every response in x-api-remaining-credits, so you never
have to ask the account what it has left — see rate limits.
The catalog
Finance 49
Text Processing 45
Data Conversion 33
Data Generation 32
Entertainment 24
Games 21
Domain Data 18
Data Lookup 17
Networking 14
Geography 13
Reference Data 11
Data Validation 9
Weather 8
Math/Calculations 8
Images 7
Transportation 6
AI/Computer Vision 6
Astrology 6
Data Processing 6
Calendar 5
Data Scraping 5
Security 4
Parsers 4
Science 4
Food 3
Lifestyle 3
Documents 3
Health/Wellness 2
News 1
Next
Pick anything above and its reference page has a working call you can paste. If you have not made one yet, quickstart is the fastest route there.
If you are calling many endpoints, the SDKs wrap all of them with one client, and batch requests run many inputs through one endpoint in a single call. For a worked example of two endpoints solving one problem, see block fake signups.
Terms used across these pages are defined in the glossary.