For agent builders

Florida business data for your agent stack, in 60 seconds

Building on Claude Code, OpenClaw, Hermes, or rolling your own MCP-compliant agent? Drop this MCP endpoint into your config. 12M+ Florida entities, ranked search, daily leads, full officer graph. Auth via Bearer. Standard MCP-1.0 JSON-RPC. $5/mo for 1K calls — perfect for prototyping; scales when you go to market.

Get MCP access — $5/mo View install docs

Florida public records · Direct from FL DOS SFTP · Updated daily

Built like an API you'd actually wire up

Boring on purpose

tools/list

Standard MCP-1.0 JSON-RPC. Lists all 8 Florida-data tools, their schemas, and arg shapes — drop-in introspection for any client.

Ask: “Call POST /mcp with method 'tools/list' to discover available Florida tools at runtime.”

Bearer auth

One header. No OAuth dance, no signed requests. Issue per-agent keys; rotate or revoke from the dashboard.

Ask: “Authorization: Bearer fbapi_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx”

JSON-RPC over HTTP

Same envelope shape as the REST API. JSON in, JSON out. Streamable responses where it matters (large entity searches).

Ask: “{ "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "search_entities", "arguments": { "name": "acme" } } }”

Three configs, same endpoint

Pick the client. Paste the snippet.

Edit your Claude Desktop config (Mac: ~/Library/Application Support/Claude/claude_desktop_config.json — Windows: %APPDATA%\Claude\claude_desktop_config.json), then restart Claude.

json

{
  "mcpServers": {
    "florida-business-api": {
      "url": "https://floridabusinessapi.com/api/mcp",
      "headers": {
        "Authorization": "Bearer fbapi_live_REPLACE_WITH_YOUR_KEY"
      }
    }
  }
}

Restart Claude Desktop. The 8 Florida tools appear in your tool list.

Or skip the client entirely

It's just HTTP + JSON-RPC

Discover the tools

A single tools/list call returns every tool, its schema, and arg types.

GET/mcp

curl -H "Authorization: Bearer fbapi_test_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" \
     "https://floridabusinessapi.com/mcp"

Sample response shape

Tool-call results return the same envelope shape as the REST API: data, meta, pagination cursors.

JSONentity-search.json

{
  "data": [
    {
      "document_number": "L20000123456",
      "entity_name": "ACME EXAMPLE LLC",
      "entity_type": "FLAL",
      "status": "Active",
      "filing_date": "2026-04-15",
      "principal_address": {
        "city": "Tampa",
        "state": "FL",
        "zip": "33602"
      }
    }
  ],
  "pagination": {
    "limit": 25,
    "offset": 0,
    "total": 1,
    "has_more": false
  },
  "meta": {
    "request_id": "req_2NkVqJtX9bL7mFp1zG4eR"
  }
}

Underlying data shapes match the REST API. If you want raw OpenAPI 3.1, jump to the API reference.

Standards, not lock-in

Open MCP spec. Works with any MCP-1.0 client today; modelcontextprotocol.io.
Bearer auth. Per-agent keys, scoped, rotatable. No OAuth choreography.
8 tools, extension PRs welcome. The tool surface is versioned; open a PR if you need a new endpoint and we'll add it on the same MCP server.

$5/mo for prototyping. Tiered when you ship.

1,000 calls a month included. Higher tiers when your agent goes to production. No retainer, no minimum, cancel anytime.

Get MCP access — $5/mo Back to MCP overview

Florida public records · Direct from FL DOS SFTP · Updated daily