Human Name Parser is a simple tool for parsing human names into their components. It returns the parsed components of the human name.
Try it — live request, no key required
GETapi.apiverve.com/v1/humannameparser
VerificationFormat
No key required to try it. Get a key to use it in your app.
{
"status": "ok",
"error": null,
"data": {
// Human Name Parser response payload
}
}Code examples — ready to paste, with real parameters
curl "https://api.apiverve.com/v1/humannameparser?name=MR.%20MARTINO%20PETROS%20DE%20FLORENCE%20(TINO)%20Jr." \
-H "x-api-key: YOUR_API_KEY"Replace
YOUR_API_KEY with your key.Full reference in the docs →
Access methods
Call it however you build.
One endpoint, many ways in — REST with JSON, XML, YAML, and CSV, plus GraphQL and an MCP interface for AI agents.
JSON
Default REST response
XML
Markup format
YAML
Human-readable
CSV
Tabular export
Beta
GraphQL
Query language
New
MCP
For AI agents
Zero-code embed
Drop it into any site.
Add an interactive form for Human Name Parser with a single snippet — no backend, no keys in your markup.
Loading preview…
What does the Human Name Parser API do?
Human Name Parser is a simple tool for parsing human names into their components. It returns the parsed components of the human name.
How do I authenticate Human Name Parser API requests?
Pass your API key in the x-api-key header over HTTPS. One key works across all 300+ APIVerve APIs — there are no per-endpoint credentials.
How much does the Human Name Parser API cost?
Each call spends 1 credit from your shared pool. The free tier includes 100 credits every month, and paid plans add more headroom.
How fast is the Human Name Parser API?
Typical responses return in around 474 ms (p50), served from 24 regions under a 99.9% uptime SLA.
What response formats does the Human Name Parser API support?
JSON by default, plus XML and YAML via the format parameter. GraphQL and an MCP interface for AI agents are available across the catalog.
What HTTP method does the Human Name Parser API use?
GET over HTTPS, following standard REST conventions with a consistent { status, error, data } response envelope.