GroundRules
Registry code: acfaf6d8f53f5a09
GroundRules serves the verbatim text of enacted law with provenance (official source URL, current-through or vintage label, retrieval time, jurisdiction). Nothing is summarized, interpreted, or ranked by importance; the calling agent interprets. Vintage-labeled text is a dated snapshot, not current law. When we do not host a jurisdiction's text, tools say exactly that and point at where it lives. Not legal advice.
- endpoint
- https://law.agentlookups.ai/mcp
- protocol
- streamable-http ·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 GroundRules live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is GroundRules free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does GroundRules have?
- 4 tools: law_search, law_for_location, law_get_section, law_coverage.
- Is GroundRules 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.
90 days 100%· all time 100%
last good check
of 4 tools
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
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.
law_coverage open 1h ago
Per-source coverage: what we host, section counts, current-through or vintage, last_verified, and a stale flag for any source the recurring verify has proven behind its upstream. Machine-generated from the build manifest; never hand-typed. Absence from this list means we do not host that jurisdiction's text, not that no law exists there.
{ "type": "object", "properties": {} }arguments 4 lineslaw_search unknown never probed
Search original law by topic, question, or citation. Exact citations resolve directly. Scoped by jurisdiction or source ids (e.g. us, us-tx; us-cfr scopes to the CFR alone, us covers both the US Code and the CFR) or by an address (the address is resolved first, then the search covers exactly its stack's hosted sources). Results are verbatim snippets with citation, official source URL, retrieval time, and a current-through or vintage label adjacent to every snippet; a hit whose source has fallen behind its upstream carries stale:true. Vintage-labeled text is a dated snapshot, not current law. Requested ids we do not host are named in the response note; law_coverage lists what is hosted.
{ "type": "object", "required": [ "q" ], "properties": { "q": { "type": "string", "description": "Topic, question, or citation" }, "mode": { "enum": [ "auto", "keyword" ], "type": "string", "description": "auto combines word and semantic retrieval when available; keyword avoids model inference." }, "limit": { "type": "integer" }, "offset": { "type": "integer" }, "address": { "type": "string", "description": "One-line street address to auto-scope the search; pass this or jurisdictions, not both" }, "sources": { "type": "string", "description": "Exact comma-separated source IDs; us = US Code only here. Use instead of jurisdictions/address." }, "include_text": { "type": "integer", "maximum": 3, "minimum": 0, "description": "Include full text for up to this many top results (0 by default; sections over 64KB require get)." }, "jurisdictions": { "type": "string", "description": "Comma-separated jurisdiction or source ids from law_coverage, e.g. us,us-tx (us-cfr = CFR only)" } } }arguments 44 lineslaw_for_location unknown 1h ago
Resolve an address or lat/lon to its full jurisdiction stack: federal, state, county, place, each with its code sources (name, publisher, official URL, current-through, whether we host its text). Unincorporated areas get the county code with no city code; about half of US municipalities publish no code online, and the answer says so and points at where the code lives if anywhere.
{ "type": "object", "properties": { "lat": { "type": "number" }, "lon": { "type": "number" }, "address": { "type": "string", "description": "One-line street address" } } }arguments 15 lineslaw_get_section unknown 1h ago
Fetch full verbatim text by id or citation, or pass references for a batch of up to 10. Each batch item has its own result/error. Includes provenance (official source URL, current-through or vintage label, retrieval time), parent path, and prev/next siblings. The text is reproduced exactly as published by the official source; nothing is added or removed except publisher editorial matter, which we never carry.
{ "type": "object", "properties": { "id": { "type": "string", "description": "Section id returned by search" }, "citation": { "type": "string", "description": "Full citation, e.g. California Civil Code 1950.5" }, "references": { "type": "array", "items": { "type": "string" }, "maxItems": 10, "minItems": 1, "description": "Batch of section ids or complete citations" } } }arguments 22 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idacfaf6d8f53f5a09.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/acfaf6d8f53f5a09/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/acfaf6d8f53f5a09?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.
Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.
- food.agentlookups.ai spoon-scout
- env.agentlookups.ai groundtruth
- solar.agentlookups.ai greenlight
- rx.agentlookups.ai counterscript
- overassessed.agentlookups.ai overassessed
- contractors.agentlookups.ai plumbline