ingest0r
ingest0r operates the Cook County (Chicago) property records API at api.ingest0r.com — a pay-per-call, agent-native REST API over Cook County, Illinois public records (~1.9M parcels, refreshed nightly) that resolves a street address to its parcel PIN, then returns parcel details, recorded sales and deed history, building permits linked to the PIN, property-tax assessment history and comparable-sales valuation as one joined answer. There is no signup and no API key: address search and a fixed sample are always free, the first 25 PIN-route calls per client per day return real data free, and past that the routes answer HTTP 402 and are settled per call in USDC on Base or Solana through the x402 protocol ($0.01, $0.03 and $0.10). The provider publishes an OpenAPI 3.1, an A2A agent card, a live streamable-HTTP MCP server with five tools, llms.txt, an x402 resource list, a machine-readable price card and changelog, and a security.txt — all on api.ingest0r.com. The operator identifies itself only as "independent" (the agent card's provider.organization) with a personal contact address; the apex ingest0r.com has no DNS A record, so the API host is the website.
ingest0r publishes 5 API contracts indexed on the APIs.io network, including Comps API, Dossier API, Parcel API, and 2 more. Tagged areas include Company, Real Estate, Property Records, Property Data, and Public Records.
ingest0r’s developer surface includes documentation, pricing, changelog, authentication, sandbox, and 25 more developer resources.
Kin Score
Standards implemented 1
Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.
APIs 5
Individual APIs this provider publishes, each with its own machine-readable definition.
Cook County (Chicago) Property Records MCP Server
A live remote MCP server at https://api.ingest0r.com/mcp (streamable-http, JSON-RPC 2.0 over HTTP POST, protocol 2025-11-25, serverInfo cook-county-chicago-property-data 1.27.2)...
ingest0r Comps API
The Comps API from ingest0r — 1 operation(s) for comps.
ingest0r Dossier API
The Dossier API from ingest0r — 1 operation(s) for dossier.
ingest0r Parcel API
The Parcel API from ingest0r — 1 operation(s) for parcel.
ingest0r Search API
The Search API from ingest0r — 1 operation(s) for search.
Arazzo Workflows 1
Multi-step API workflows described with the Arazzo specification.
Cook County address to dossier and comps
Resolve a street address to its parcel PIN, fetch the full property dossier, then fetch comparable sales and an implied value range.
ARAZZOMCP Servers 1
Model Context Protocol servers that expose these APIs to AI agents.
Pricing Plans 1
Published pricing tiers and plan structures.
Rate Limits 1
Documented rate limits and quota policies.
Ingest0R Com Rate Limits
RATE LIMITSOpenAPI Overlays 1
Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.
Ingest0R Com Openapi Overlay
UNRECORDEDSecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
Recommended x-agentic-access execution contracts for AI agents.
Resources
Get Started 1
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 6
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Other 2
Properties that don't map to a standard resource type
Source (apis.yml)
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.