Properties
| Name | Type | Description |
|---|---|---|
| verdict | string | Decision about the number, e.g. rejected |
| risk_score | integer | Risk score associated with the number |
| evidence_coverage | integer | Percentage of evidence coverage |
| credits | integer | Credits consumed for the lookup |
| recommendation | string | Suggested action for the caller |
| capability | string | Capability state, e.g. VERIFIED |
| state | string | State of the validation, e.g. Format VERIFIED |
| format | string | Result of format parsing |
| plan_validity | string | Validity of the numbering plan |
| carrier | string | Carrier information (if available) |
| reachability | string | Reachability status (if available) |
| source | string | Source of the evidence, e.g. National regulator allocations |
| line_type | string | Type of line (fixed line or mobile) derived from the numbering plan |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://raw.githubusercontent.com/api-evangelist/orisift/main/json-schema/orisift-post-v1-lookup-response-schema.json",
"title": "PostV1LookupResponse",
"x-generated": "2026-09-28",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/_ae-authored/orisift-openapi-generated.yml#/components/schemas/PostV1LookupResponse",
"type": "object",
"properties": {
"verdict": {
"type": "string",
"description": "Decision about the number, e.g. rejected"
},
"risk_score": {
"type": "integer",
"description": "Risk score associated with the number"
},
"evidence_coverage": {
"type": "integer",
"description": "Percentage of evidence coverage"
},
"credits": {
"type": "integer",
"description": "Credits consumed for the lookup"
},
"recommendation": {
"type": "string",
"description": "Suggested action for the caller"
},
"capability": {
"type": "string",
"description": "Capability state, e.g. VERIFIED"
},
"state": {
"type": "string",
"description": "State of the validation, e.g. Format VERIFIED"
},
"format": {
"type": "string",
"description": "Result of format parsing"
},
"plan_validity": {
"type": "string",
"description": "Validity of the numbering plan"
},
"carrier": {
"type": "string",
"description": "Carrier information (if available)"
},
"reachability": {
"type": "string",
"description": "Reachability status (if available)"
},
"source": {
"type": "string",
"description": "Source of the evidence, e.g. National regulator allocations"
},
"line_type": {
"type": "string",
"description": "Type of line (fixed line or mobile) derived from the numbering plan"
}
}
}
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/orisift-post-v1-lookup-response"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
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.