Most public-records data lives behind a REST API that your code has to call and wire into your agent. Amalgament is MCP-native, so the agent itself, Claude, ChatGPT, or Cursor, can search records, resolve entities, and pull filings mid-conversation with no integration layer.
There is a real fork when you build an agent on public data: take a plain REST data API and hand-build the tool definitions, auth, and response parsing to make it agent-usable, or connect an MCP server the agent already knows how to call. The second path is why Amalgament ships an MCP server, not just an API.
| REST-only API | Amalgament | |
|---|---|---|
| Who calls it | Your application code | The agent decides when to call it, mid-conversation |
| Integration | You write tool definitions, handle auth, parse responses | Two lines of MCP config |
| Clients | Whatever you build | Any MCP-capable client: Claude, ChatGPT, Cursor |
| Data | Varies by provider | US public records across 57 types, joined into one graph |
| Freshness | Depends on the provider | Self-refreshing; /freshness is itself a callable tool |
A REST API is called by code a developer writes. An MCP server is called by the model itself, which reads the tool descriptions and decides when to use them. For agentic workflows, a KYB agent, a due-diligence copilot, a property-research assistant, that difference removes the entire integration layer: the agent reasons, and Amalgament supplies ground truth on demand.
A KYB agent that verifies a business against registries, licenses, and watchlists as it talks to a user. A diligence copilot that pulls filings, liens, and awards on a counterparty in one thread. A property assistant that resolves an address to its parcel, owner, and permit history. All without writing a data-integration layer.
MCP-native does not mean agent-only. Amalgament exposes the same joined data as typed REST endpoints for your application code and as an MCP server for your agent, so you use whichever fits and both read the same graph.
MCP server · Learn: what is an MCP server · API documentation
Add the Amalgament MCP server to your client's config; the setup is on the MCP page. Because MCP is an open standard, the same server works across any MCP-capable client.
Amalgament offers both. It is a REST API for your code and an MCP server for your agent, over the same joined public-records graph, so you are not choosing one or the other.
More comparisons: vs OpenCorporates · vs Scraping it yourself