Name Parser

Split a full name into title, first, middle and last names, suffix and nickname. Returns the parsed name components.

Pay by wallet (x402) name-parse

Example

Example answer
{
  "prefix": null,
  "suffix": null,
  "nickname": null,
  "full_name": "test",
  "last_name": null,
  "first_name": "test",
  "middle_name": null
}

Inputs

FieldTypeRequiredWhat it is
full_namestringYesFull name to parse

Output fields

How reliably each field appears in a successful answer.

FieldTypeAppears
prefixstringUsually (present for most inputs)
suffixstringUsually (present for most inputs)
nicknamestringUsually (present for most inputs)
full_namestringAlways (present in every successful answer)
last_namestringAlways (present in every successful answer)
first_namestringAlways (present in every successful answer)
middle_namestringUsually (present for most inputs)

How to call it

The same tool through each route. MCP clients reach it through Strale’s server at https://api.strale.io/mcp; the call below is what the agent sends.

# Needs an API key. max_price_cents caps what this call may cost.
curl -X POST https://api.strale.io/v1/do \
  -H "Authorization: Bearer $STRALE_API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{
    "capability_slug": "name-parse",
    "inputs": {
      "full_name": "Dr. John Robert Smith Jr."
    },
    "max_price_cents": 3
  }'

Limitations

  • Compound and unfamiliar name formats can be misread

    AI-powered name parsing — compound surnames, cultural naming conventions, and honorifics may be split incorrectly

    What to do instead: Provide locale or cultural context in the input to improve parsing accuracy for non-Western name formats