Properties
| Name | Type | Description |
|---|---|---|
| first_name | string | Must contain at least one letter AFTER normalization, which spells the name in a-z: accents are dropped and letters such as `ø`, `æ`, `ß`, `ł` and `þ` are written `o`, `ae`, `ss`, `l` and `th`; then o |
| last_name | string | Must contain at least one letter AFTER normalization, which spells the name in a-z: accents are dropped and letters such as `ø`, `æ`, `ß`, `ł` and `þ` are written `o`, `ae`, `ss`, `l` and `th`; then o |
| domain | string | The company's mail domain, as a bare name. A special-use name (`.example`, `.test`, `.invalid`, `.localhost`, `.local`, `.onion`, `.alt`, `.internal`, `.corp`, `.home`, `.mail`, `home.arpa` and the ot |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://artifacts.apis.io/kawaa-com/json-schema/kawaa-com-find-request-schema.json",
"title": "FindRequest",
"x-generated": "2026-11-10",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/kawaa-com-search-api-openapi.yml#/components/schemas/FindRequest",
"type": "object",
"properties": {
"first_name": {
"type": "string",
"maxLength": 64,
"description": "Must contain at least one letter AFTER normalization, which spells the name in a-z: accents are dropped and letters such as `ø`, `æ`, `ß`, `ł` and `þ` are written `o`, `ae`, `ss`, `l` and `th`; then only `a-z` is kept. `José`, `Ñuñez` and `Søren` are fine, `李`, `2024` and `!!` are not. A name that normalizes to nothing generates no candidate addresses, so the API answers `400 first_name and last_name must contain letters (a-z)` and charges nothing. A name with a letter that has no single a-z spelling (such as `ə` or `ʒ`) next to letters that do is also a 400 that charges nothing, and so is one that spells to more than 64 letters. Deliberately not a `pattern` here: the check runs on the normalized form, and a regex over the raw string would refuse names this API accepts."
},
"last_name": {
"type": "string",
"maxLength": 64,
"description": "Must contain at least one letter AFTER normalization, which spells the name in a-z: accents are dropped and letters such as `ø`, `æ`, `ß`, `ł` and `þ` are written `o`, `ae`, `ss`, `l` and `th`; then only `a-z` is kept. `José`, `Ñuñez` and `Søren` are fine, `李`, `2024` and `!!` are not. A name that normalizes to nothing generates no candidate addresses, so the API answers `400 first_name and last_name must contain letters (a-z)` and charges nothing. A name with a letter that has no single a-z spelling (such as `ə` or `ʒ`) next to letters that do is also a 400 that charges nothing, and so is one that spells to more than 64 letters. Deliberately not a `pattern` here: the check runs on the normalized form, and a regex over the raw string would refuse names this API accepts."
},
"domain": {
"type": "string",
"description": "The company's mail domain, as a bare name. A special-use name (`.example`, `.test`, `.invalid`, `.localhost`, `.local`, `.onion`, `.alt`, `.internal`, `.corp`, `.home`, `.mail`, `home.arpa` and the other special-use `.arpa` names) and RFC 2606's `example.com` / `.net` / `.org` with any name under them are a 400 before the charge: no mailbox can exist there. So are a domain that cannot receive mail (no such domain, a null MX, or neither an MX nor an address record) and a public mailbox provider such as gmail.com."
}
},
"required": [
"first_name",
"last_name",
"domain"
],
"additionalProperties": false
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/kawaa-com-find-request"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.