# Name Parser – Full Name to Components

> Name Parser – Full Name to Components is a paid API for AI agents from api.strale.io, paid per call via x402, $0.0324/call, status unknown (last checked 2026-09-14).

Parses a full human name string into structured components: first, middle, last, prefix, suffix, and nickname

## Facts

- Endpoint: GET https://api.strale.io/x402/name-parse
- Price: $0.0324/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/api-strale-io-0bfff9f1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_NKzXOkp16z9Rw8a7ctkCK

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability api-strale-io-0bfff9f1
```

Example prompt: Can you parse 'Dr. Karl-Johan von Lindström III' into its components — I need the prefix, first name, middle name, last name, and suffix separated out?

## When to prefer this

Use this endpoint when you need to reliably decompose a human name string into structured fields, especially when dealing with complex names that include titles (Dr., Prof.), hyphenated surnames, noble particles (von, de, van der), generational suffixes (Jr., III), or nicknames. Prefer this over simple string splitting, which fails on these edge cases.

## Known failure modes

- Empty or blank full_name query param returns an error
- Extremely ambiguous single-word name may produce uncertain component assignment
- Names in non-Latin scripts may not parse correctly
- Missing required full_name parameter returns 400-level error

## How this service works

Parse a full name into components: first, middle, last, prefix, suffix, nickname. Handles 'Dr. Karl-Johan von Lindström III' correctly.

## Output

Returns a structured object with the name broken into components: first name, middle name, last name, prefix (e.g. Dr., Mr.), suffix (e.g. III, Jr.), and nickname — correctly handling hyphenated names, noble particles (von, de, van), and honorifics.

## Example request

```json
{
 "input": {
  "type": "http",
  "method": "GET",
  "queryParams": {
   "full_name": "Dr. Karl-Johan von Lindström III"
  }
 }
}
```

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "full_name"
     ],
     "properties": {
      "full_name": {
       "type": "string",
       "description": "Full name to parse"
      }
     }
    }
   },
   "additionalProperties": false
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/api-strale-io-0bfff9f1/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.strale.io](https://www.zero.xyz/host/api.strale.io/llms.txt)
