Akil MCP acts as a civic semantic layer for NYC public records, giving AI agents a structured way to investigate funding, property, procurement, lobbying, land use, licensing, housing, and neighborhood context. Start with akil_platform_guide for orientation, then use akil_overview to route specific civic questions.
https://mcp.askakil.ai/mcpThe useful part is not just the number of tools. It is that agents can start from a real-world anchor and receive records with identifiers, interpreted meaning, source context, caveats, and next steps.
Agents query public records directly instead of relying on web snippets, memory, or broad search results.
Fields that are easy to misread come back with plain-English context, so a filing, deadline, payment, status, or empty result is not treated as more than it is.
Each answer surfaces identifiers and next checks that connect one public system to another: BBL, EIN, agency, license, district, fiscal year.
Akil's trust checks look for public-record mistakes that agents can easily make: treating a filing as clearance, a name match as identity, a capped page as the full universe, or an empty result as proof that nothing exists.
Checks whether tool answers keep source names, filters, result caps, freshness notes, caveats, and verification paths visible.
Checks whether windowed, capped, empty, or timed-out responses are framed as bounded source results instead of full clearance.
Checks whether names, owners, vendors, licensees, applicants, permits, payments, and certifications stay separate unless source anchors support a match.
Users don't start with database names. They start with a lease, a building, a vendor, a nonprofit, an agency, a campaign, or a map. Akil translates that into the right public-record path.
Akil is designed so an assistant can move from one dataset to the next without losing the subject of the question.
Akil does not just hand an agent a row of data. It keeps the source value, plain-English meaning, caveats, identifiers, and next checks together so the answer stays useful after the first reply.
BBL 1012970023
DOB filings, certificate-of-occupancy records, violations, PLUTO, ACRIS, and nearby license records.
Separates a filing from an approval, a permit from a signoff, and a missing row from proof that nothing exists.
Not legal clearance. Confirm final status with the agency, lease counsel, or the right licensed professional.
Check CO/legal use, open violations, recent filings, and license-radius constraints.
{
"type": "akil.record_packet.v1",
"anchor": {
"kind": "property",
"bbl": "1012970023"
},
"finding": {
"source": "NYC DOB",
"sourceValue": "Application filed",
"meaning": "A filing exists. It is not the same as an approved permit or final signoff."
},
"caveat": "Verify current status before relying on this for a lease or closing.",
"nextChecks": [
"certificate of occupancy",
"open violations",
"license fit"
]
}Examples of good starting points. Each begins with an anchor; the assistant follows the relevant public-record path from there.
Client support varies by AI product. Use the connector interface provided by your client when available; Akil remains one protected remote MCP endpoint.
Add Akil as a custom connector, paste the MCP URL, and sign in when prompted.
Start from an address, organization, district, person, program, agency, license, or question.