_ registry / mcp + a2a http-sse · checked 39m ago

permit-intelligence

https://permit-api-production-7375.up.railway.app

Registry code: 81aec508dd7bb37b

api record

Building-permit verdicts by address, with cited records. SF, Seattle, Austin, NYC. Pay per call.

from a public catalogue that lists it, not from the operator

endpoint
https://permit-api-production-7375.up.railway.app/mcp
door code
657d5998f0500138
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is permit-intelligence live?
Yes — it answered the hub's last check (checked 39m ago). It answered 100% of checks over the last 30 days.
Is permit-intelligence free to use?
Yes — the hub reached it with no key and no payment.
What tools does permit-intelligence have?
10 tools: attest_price_event, check_permit_activity, find_active_projects, resolve_price_event, get_crypto_spot, decode_decision_id, verify_decision, get_permit_verdict, ….
Is permit-intelligence safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.6%

90 days 99.1%· all time 99.3%

latency
328ms

last good check

priced tools
0

of 10 tools

_ answered our checks, 90 days 1293 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
real estate & construction property & real estate
used for
  • check building permits for an address
  • find active construction projects
  • resolve a crypto price event
takes → gives
text → data
tools
9 reads1 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address also stands behind 2 other origins: the chain figures are the gateway's, not this listing's alone. How it is counted.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

payers on base
5

distinct

settlements
15

last 2026-10-19

received on chain
0.207 USDC

concentrated, shared-payto

_ what it can do 10 tools
1 open 9 never probed 1 of 10 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_jurisdictions reads open 17h ago

    List cities covered by the Permit Intelligence API, with pricing and payment details. Free. Full paid feeds for humans: https://permitverdict.com/pricing

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • attest_price_event changes data unknown 12h ago

    Settlement verdict plus a citable record: a signed decision_id, an integrity hash over the evidence, and every candle that determined the outcome. Use this when the answer may later have to be defended to a counterparty, not when you just need to know. KEEP THE decision_id — it is self-contained, so anyone you show it to can authenticate it for free and re-check it for $0.02 without you supplying anything else. Paid: $0.25 in USDC via x402.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "asset",
    "operator",
    "threshold"
  ],
  "properties": {
    "to": {
      "type": "string",
      "description": "ISO-8601 window end. Defaults to now."
    },
    "from": {
      "type": "string",
      "description": "ISO-8601 window start. Defaults to 24h before `to`."
    },
    "mode": {
      "enum": [
        "touch",
        "close"
      ],
      "type": "string",
      "description": "touch (default) or close"
    },
    "asset": {
      "type": "string",
      "description": "Asset symbol, e.g. BTC, ETH, SOL"
    },
    "operator": {
      "enum": [
        "above",
        "at_or_above",
        "below",
        "at_or_below"
      ],
      "type": "string",
      "description": "Comparison against the threshold"
    },
    "threshold": {
      "type": "number",
      "description": "Price threshold in USD",
      "exclusiveMinimum": 0
    },
    "payment_header": {
      "type": "string",
      "description": "X-PAYMENT header from a settled x402 payment."
    }
  }
}
    arguments 50 lines
  • check_permit_activity reads unknown 12h ago

    FREE. Quick check on whether a street address has building-permit activity on record: how many permits, how many are open, and when the last activity was. No permit detail and no verdict — use get_permit_verdict for those. Full paid feeds for humans: https://permitverdict.com/pricing

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "jurisdiction",
    "address"
  ],
  "properties": {
    "address": {
      "type": "string",
      "minLength": 3,
      "description": "Street address, e.g. '760 14th St'"
    },
    "jurisdiction": {
      "enum": [
        "san_francisco",
        "seattle",
        "austin",
        "nyc",
        "chicago",
        "los_angeles",
        "new_orleans"
      ],
      "type": "string",
      "description": "Covered city, e.g. san_francisco"
    }
  }
}
    arguments 28 lines
  • find_active_projects reads unknown 17h ago

    FREE PREVIEW (5 results). Recently permitted construction projects in a covered city, filtered by declared budget. Use feed='investor' instead to surface expired and abandoned permits (stalled projects, often motivated owners). Full paid feeds for humans: https://permitverdict.com/pricing

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "jurisdiction"
  ],
  "properties": {
    "days": {
      "type": "integer",
      "maximum": 180,
      "minimum": 1,
      "description": "Lookback window, default 30"
    },
    "feed": {
      "enum": [
        "contractor",
        "investor"
      ],
      "type": "string",
      "description": "contractor = newly filed/issued permits (default); investor = expired/stalled"
    },
    "max_cost": {
      "type": "number",
      "minimum": 0,
      "description": "Maximum declared job value, 0 = no ceiling"
    },
    "min_cost": {
      "type": "number",
      "minimum": 0,
      "description": "Minimum declared job value, default 50000"
    },
    "jurisdiction": {
      "enum": [
        "san_francisco",
        "seattle",
        "austin",
        "nyc",
        "chicago",
        "los_angeles",
        "new_orleans"
      ],
      "type": "string",
      "description": "Covered city, e.g. san_francisco"
    }
  }
}
    arguments 46 lines
  • resolve_price_event reads unknown 15h ago

    Settlement verdict for a crypto price event. Answers 'did this asset trade or close above/below a threshold during a window?' with YES/NO/DISPUTED/UNRESOLVED, per-venue evidence from Hyperliquid, Coinbase and Kraken, and stated confidence. (Binance is configured but blocks this host's region; it is reported unavailable rather than silently counted.) Use mode='close' when a market settles on candle closes and mode='touch' when any intrabar print counts — they give different answers and that difference is the most common settlement dispute. Paid: $0.05 in USDC via x402.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "asset",
    "operator",
    "threshold"
  ],
  "properties": {
    "to": {
      "type": "string",
      "description": "ISO-8601 window end. Defaults to now."
    },
    "from": {
      "type": "string",
      "description": "ISO-8601 window start. Defaults to 24h before `to`."
    },
    "mode": {
      "enum": [
        "touch",
        "close"
      ],
      "type": "string",
      "description": "touch = any intrabar print counts (default); close = only candle closes count"
    },
    "asset": {
      "type": "string",
      "description": "Asset symbol, e.g. BTC, ETH, SOL"
    },
    "operator": {
      "enum": [
        "above",
        "at_or_above",
        "below",
        "at_or_below"
      ],
      "type": "string",
      "description": "Comparison against the threshold"
    },
    "threshold": {
      "type": "number",
      "description": "Price threshold in USD",
      "exclusiveMinimum": 0
    },
    "payment_header": {
      "type": "string",
      "description": "X-PAYMENT header from a settled x402 payment. Omit on first call to receive payment requirements."
    }
  }
}
    arguments 50 lines
  • get_crypto_spot reads unknown 15h ago

    Live cross-venue spot price with venue agreement and spread. A wide spread means venues disagree and any settlement in that range is contestable. Paid: $0.01 in USDC via x402.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "asset"
  ],
  "properties": {
    "asset": {
      "type": "string",
      "description": "Asset symbol, e.g. BTC, ETH, SOL"
    },
    "payment_header": {
      "type": "string",
      "description": "X-PAYMENT header from a settled x402 payment."
    }
  }
}
    arguments 17 lines
  • decode_decision_id reads unknown 17h ago

    FREE. Read what a Permit Verdict decision_id claims and check whether we actually issued it. The id is signed by the same wallet that receives payment, so forgery and after-the-fact editing are both detectable. Needs no payment. This tells you the record is genuine; it does NOT tell you the verdict is still correct — use verify_decision for that. Full paid feeds for humans: https://permitverdict.com/pricing

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "decision_id"
  ],
  "properties": {
    "decision_id": {
      "type": "string",
      "description": "A decision_id of the form pv1.<payload>.<signature>"
    }
  }
}
    arguments 13 lines
  • verify_decision reads unknown 12h ago

    Re-resolve an attested settlement against the price venues right now and report whether it still holds: CONFIRMED, CHANGED or INDETERMINATE. Call this whenever someone hands you a decision_id you are about to rely on — an attestation proves what was said at the time, but only a fresh resolution proves it is still true. Exchanges revise candle history, and a venue that was unreachable at issue time may answer differently now. Paid: $0.02 in USDC via x402 — cheaper than resolving fresh because you are checking someone else's answer rather than buying a new one.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "decision_id"
  ],
  "properties": {
    "decision_id": {
      "type": "string",
      "description": "A decision_id issued by /v1/oracle/attest"
    },
    "payment_header": {
      "type": "string",
      "description": "X-PAYMENT header from a settled x402 payment. Omit on first call to receive payment requirements."
    }
  }
}
    arguments 17 lines
  • get_permit_verdict reads unknown 15h ago

    Address-level building-permit intelligence for a covered city: normalized permit history + activity signals + a decision-ready verdict with cited public records. Paid: $2.00 in USDC on base via x402.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "jurisdiction",
    "address"
  ],
  "properties": {
    "address": {
      "type": "string",
      "minLength": 3,
      "description": "Street address, e.g. '760 14th St'"
    },
    "jurisdiction": {
      "enum": [
        "san_francisco",
        "seattle",
        "austin",
        "nyc",
        "chicago",
        "los_angeles",
        "new_orleans"
      ],
      "type": "string",
      "description": "Covered city, e.g. san_francisco"
    },
    "payment_header": {
      "type": "string",
      "description": "Optional X-PAYMENT header value from a completed x402 payment. Omit on first call to receive payment requirements."
    }
  }
}
    arguments 32 lines
  • list_settlement_assets reads unknown never probed

    FREE. Which crypto assets, venues, operators and modes the settlement oracle supports, plus pricing. Full paid feeds for humans: https://permitverdict.com/pricing

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
_ try it over mcp through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 81aec508dd7bb37b.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/81aec508dd7bb37b/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/81aec508dd7bb37b/badge.svg)](https://brick.blue/agent/81aec508dd7bb37b?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we knowoff the mcp door
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.