{"id":"ai.tunnelmind/data","slug":"ai-tunnelmind-data","title":"TunnelMind Data API","description":"Tracker / Sigil / Cross-lens — every TunnelMind Data API operation as one MCP surface.","version":"1.0.1","publisher":{"kind":"domain","id":"tunnelmind.ai","label":"tunnelmind.ai","url":"https://tunnelmind.ai"},"website":"https://tunnelmind.ai","repository":"","remotes":[{"type":"streamable-http","url":"https://mcp-data.tunnelmind.ai/mcp"}],"packages":[],"published":"2026-08-03","updated":"2026-08-03","status":"online","auth":"","latency_ms":1530,"checked":"2026-11-19","uptime":100,"checks":3,"tools":[{"name":"health_check","title":"","description":"Returns a minimal status object confirming the API is alive. Use this to verify\nconnectivity before chaining other calls, or as a liveness check in a workflow.\n\nUse this tool when:\n- You need to verify the API is reachable before starting a multi-step investigation.\n- A prior call failed with a 503 or 504 and you want to confirm the service recovered.\n- You are debugging connectivity from a new en","read_only":false},{"name":"get_domain","title":"","description":"Returns the complete surveillance intelligence record for a domain name. If the\ndomain is in TunnelMind's tracker database (80,000+ entries), the response includes\ntracker category, risk score, fingerprinting data, cookie persistence, IAB TCF\npurposes, and the owning corporate entity. If the domain is not in the database,\na live probe is automatically run: RDAP registration data, DNS records (MX, ","read_only":false},{"name":"list_domains","title":"","description":"Returns a paginated list of domains from the tracker database. Results are ordered\nalphabetically by domain name and support cursor-based pagination for full traversal.\nFiltering by category and minimum score allows targeted data extraction.\n\nUse this tool when:\n- You want to enumerate all known ad-tech or analytics domains above a risk threshold.\n- You need a dataset of tracker domains for offlin","read_only":false},{"name":"get_entity","title":"","description":"Returns an entity record for a surveillance company or data broker, including its\nindustry, estimated annual data value per user (in USD), categories of personal data\ncollected, and the full list of domains it controls. Free tier returns 5 domains,\npaid returns up to 200.\n\nUse this tool when:\n- You want to understand what corporate entity owns or controls a tracker domain.\n- You need to assess the","read_only":false},{"name":"list_entities","title":"","description":"Returns a paginated list of corporate entities in the TunnelMind surveillance\ndatabase. Includes data categories, estimated data value, and industry classification.\nUseful for enumerating the surveillance ecosystem by sector.\n\nUse this tool when:\n- You want to enumerate all entities in a specific industry (e.g., all ad-tech companies).\n- You need a dataset of surveillance entities for analysis or ","read_only":false},{"name":"search","title":"","description":"Searches both the domains table and the entities table simultaneously. Returns\nmatching domains (by domain name) and entities (by name or slug) in a single\nresponse. Minimum 2 characters, maximum 100 characters.\n\nUse this tool when:\n- You have a partial name and need to identify what tracker or entity it belongs to.\n- You want to find all TunnelMind records related to a company name like \"Google\" ","read_only":false},{"name":"intel_http","title":"","description":"Makes a live HEAD request to the target domain from the Cloudflare edge, follows\nup to 5 redirects, and returns the full redirect chain, final HTTP status, key\nresponse headers, a security header score, and any third-party surveillance\nactors referenced in the Content-Security-Policy header.\n\nUse this tool when:\n- You want to verify whether a site enforces HTTPS and HSTS.\n- You need to inspect wha","read_only":false},{"name":"intel_stack","title":"","description":"Fetches up to 32KB of the domain's HTML and response headers from the edge, then\nfingerprints the content for known CMS platforms, JavaScript frameworks, CDN\nproviders, and analytics tools. Detection is based on meta generator tags, script\nsrc patterns, response headers, and cookie names.\n\nUse this tool when:\n- You need to know what CMS (WordPress, Drupal, Shopify) a site runs.\n- You are assessing","read_only":false},{"name":"intel_robots","title":"","description":"Retrieves the target domain's `robots.txt` file and parses it for AI crawler\ndisallow rules. Specifically detects policies for known AI crawlers (GPTBot,\nClaudeBot, CCBot, Bytespider, etc.) and returns a structured summary of the\ncrawling policy.\n\nUse this tool when:\n- You need to know whether a domain has opted out of AI training data collection.\n- You want to check if a specific AI crawler is bl","read_only":false},{"name":"intel_agent","title":"","description":"Probes a domain for known AI agent integration signals: `llms.txt`, `ai.txt`,\n`/.well-known/ai-plugin.json`, `openapi.json`, `swagger.json`, MCP manifest, MCP\nSSE endpoint. Returns a score based on the count of signals detected. Use this to\nassess whether a domain is ready for agent-to-agent interaction.\n\nUse this tool when:\n- You want to know whether a domain exposes an MCP server or OpenAPI spec","read_only":false},{"name":"intel_inject","title":"","description":"Fetches a domain's homepage and checks for content patterns that could constitute\nprompt injection attacks against AI agents that visit and ingest the page. Signals\ninclude hidden text, invisible divs, `<!-- AI: ignore -->` style comments, and\nknown injection patterns.\n\nUse this tool when:\n- You are vetting a domain before feeding its content into an LLM context.\n- You want to assess the prompt in","read_only":false},{"name":"intel_optout","title":"","description":"Checks a domain for all known AI training data opt-out mechanisms beyond robots.txt:\nTDM (Text and Data Mining) reservation headers, `<meta name=\"ai\">` tags, Creative\nCommons NonCommercial licenses, and other machine-readable opt-out signals.\n\nUse this tool when:\n- You need to determine whether a domain has opted out of AI training data collection.\n- You are checking compliance before using a doma","read_only":false},{"name":"get_receipt","title":"","description":"Returns metadata for a TunnelMind surveillance receipt — a signed document proving\nthat a specific user's surveillance exposure was observed, measured, and recorded at\na specific time. Does NOT return the receipt's signature (anti-phishing protection).\nTo verify a receipt's content integrity, use `verify_receipt` with the hash and\nsignature from the receipt document itself.\n\nUse this tool when:\n- ","read_only":false},{"name":"verify_receipt","title":"","description":"Tamper-detection verification for TunnelMind surveillance receipts. Submit the\nreceipt ID, the SHA-256 content hash, and the Ed25519 signature from the receipt\ndocument. The registry compares these against what was recorded at issuance time.\nReturns VALID if both match exactly, INVALID with a specific mismatch reason otherwise.\n\nUse this tool when:\n- You received a surveillance receipt document an","read_only":false},{"name":"create_free_key","title":"","description":"Self-serve free tier — the rung between anonymous access and paid\nblocks. One email in, one API key out, shown exactly once.\n\nUse this tool when:\n- You are calling anonymously and hitting the anonymous rate limit.\n- You want your calls identified so usage survives IP changes.\n\nLimits:\n- 50 requests/day, counted per key rather than per IP (same endpoints\n  as anonymous; anonymous is 10/min and 100/","read_only":false},{"name":"get_api_key","title":"","description":"Returns the tier, label, masked owner email, creation date, last-used timestamp,\ntoday's request count, and daily request limit for the API key used in this request.\nUseful for agents that need to monitor their own quota consumption.\n\nUse this tool when:\n- You want to check how many requests your key has used today.\n- You need to know your current tier or daily limit.\n- You want to confirm that yo","read_only":false},{"name":"revoke_api_key","title":"","description":"Permanently deactivates the API key used to make this request. This action is\nirreversible. After revocation, the key will return 401 on all subsequent calls.\n\nUse this tool when:\n- You want to rotate your API key (revoke old, then provision a new one).\n- You believe your key has been compromised.\n\nDo NOT use this tool when:\n- You want to check quota — use `get_api_key` instead.\n- You intend to ke","read_only":false},{"name":"get_task","title":"","description":"Returns the current status of a task created by an `?async=true` intel request.\nPoll this endpoint until `status` is one of: `complete`, `failed`, `cancelled`,\n`expired`. On `complete`, the `result` field contains the same payload the sync\nendpoint would have returned. On `failed`, `error.message` explains the failure.\n\nUse this tool when:\n- You submitted an intel probe with `?async=true` and need","read_only":false},{"name":"cancel_task","title":"","description":"Marks the task as `cancelled`. If the task is already in a terminal state\n(`complete`, `failed`, `expired`), returns 409 Conflict. Only the identity\nthat created the task may cancel it.\n\nUse this tool when:\n- You submitted a probe with `?async=true` and no longer need the result.\n- You want to free up a pending task before it expires.\n\nDo NOT use this tool when:\n- The task is already complete — ca","read_only":false},{"name":"stream_task","title":"","description":"Opens a persistent SSE connection that emits events as the task progresses.\nThe stream closes automatically when the task reaches a terminal state or after\n~90 seconds (timeout). Heartbeat comments are sent every ~15 seconds to keep\nthe connection alive through proxies.\n\nEvent types:\n- `status` — emitted when status changes (pending → running → complete/failed)\n- `result` — emitted on `complete` w","read_only":false},{"name":"audit_export","title":"","description":"Returns NDJSON (one JSON object per line) of audit log entries. Each entry records\nthe operation called, the identity, hashes of the request and response, duration,\nand an Ed25519 signature over the canonical entry JSON. Entries are hash-chained:\neach entry's `prev_entry_hash` is SHA-256 of the previous entry's signature,\nmaking deletion of any entry detectable offline.\n\nAuthenticated callers rece","read_only":false},{"name":"generate_receipt","title":"","description":"At least one of `domains` (or `domain`) is required.\n\nLooks up each submitted domain in the TunnelMind tracker database, aggregates risk\nmetrics (avg score, max score, fingerprinters, high-risk domains, entity ownership),\nand issues a signed surveillance receipt. The receipt is stored in the public registry\nand can be verified at `/verify/{receipt_id}`.\n\nUse this tool when:\n- You want a verifiable","read_only":false},{"name":"sigil_verify_ads_txt","title":"","description":"Confirms whether an SSP/exchange is authorized to sell a publisher's\ninventory according to that publisher's ads.txt. This is a cache lookup\nagainst ads.txt files crawled daily across the top 10,000 publisher\ndomains — it does NOT fetch the publisher's ads.txt live, so it is fast\nand adds no latency to a real-time bidding decision.\n\nUse this tool when:\n- You are an ad-buying agent and want to conf","read_only":false},{"name":"sigil_verify_ads_txt_batch","title":"","description":"Runs up to 100 ads.txt verifications in a single call — the endpoint an\nad-buying agent uses for pre-bid checks across a whole campaign's supply.\nEach item is the same shape as `sigil_verify_ads_txt`. Per-item\nvalidation failures are reported inline; the batch never fails as a\nwhole. Publisher records are fetched once per unique domain.\n\nUse this tool when:\n- You are evaluating many supply paths a","read_only":false},{"name":"traction","title":"","description":"Live traction numbers computed from sources the Worker owns: the\nhash-chained D1 audit log (7-day call volume, distinct identified\ncallers, top operations), the stored-receipt table, and Stripe\n(succeeded charges → paying customers, gross USD). Ed25519-signed\nwith the same attestation envelope as /v1/status so the numbers can\nbe replayed to an auditor.\n\nUse this tool when:\n- You are evaluating whe","read_only":false},{"name":"fareseal_stats","title":"","description":"The public read over the Conduct Log Commons: which agents knocked on\nattested Fareseal sites in the last 7 days, what they did when offered\npaid access, and what they would have paid. First-party monitors and\ncredential-scanning recon are classified and EXCLUDED from the headline\n(reported separately, never conflated). Attested tier only — keys a\ndomain has vouched for via /.well-known/fareseal-s","read_only":false},{"name":"fareseal_export","title":"","description":"Free bulk read of the commons — the raw record is never paywalled. Every\nrow carries a Fareseal document exactly as its site signed it — the\n`receipt` (kind=receipts) or `snapshot` (kind=reports) object, Ed25519\nover RFC 8785 JCS of that document minus `sig`, key = its own `site` —\nbeside a `_commons` envelope naming the tier and vouching domain (the\nenvelope is not signed). Nothing in a row requi","read_only":false},{"name":"fareseal_sites","title":"","description":"Membership of the commons: every signing key that has reported, the\ndomain that vouched for it (by serving the key in its\n/.well-known/fareseal-site.json), and when it was last re-checked.\nAttested only by default; tier=all adds unattested keys with the domain\nthey CLAIMED but that did not (yet) vouch for them.\n\nUse this tool when:\n- You want to know whose data is in the exhibit, or whether a give","read_only":false},{"name":"fareseal_agents","title":"","description":"Spec 125, the agent conduct record. Every agent public key that an\nattested Fareseal site reported, with its summed request count,\nnewest first. Free, no auth, attested tier only. Facts, not verdicts:\nno score, no tier, no IP. Counts are a LOWER BOUND (an evicted entry or\na restarted isolate loses history Fareseal never reported).\n\nUse this tool when:\n- You want to know which agents the commons ha","read_only":false},{"name":"agent_record","title":"","description":"Spec 125. One agent public key's record across attested Fareseal\nsites: summed requests, a sample of paths, whether robots.txt was\nfetched, the signed snapshots each figure comes from (`sources[]`),\nand the newest 100 receipts naming the key, verbatim. Free, no auth.\nFacts, not verdicts: no score, no tier, no IP. Counts are a LOWER\nBOUND. The cache is not the record — `verify` says how to recomput","read_only":false},{"name":"tollbooth_stats","title":"","description":"Deprecated alias of fareseal_stats. Same data; use the /v1/fareseal/ path. Original description follows.\n\nThe public read over the Conduct Log Commons: which agents knocked on\nattested Fareseal sites in the last 7 days, what they did when offered\npaid access, and what they would have paid. First-party monitors and\ncredential-scanning recon are classified and EXCLUDED from the headline\n(reported se","read_only":false},{"name":"tollbooth_export","title":"","description":"Deprecated alias of fareseal_export. Same data; use the /v1/fareseal/ path. Original description follows.\n\nFree bulk read of the commons — the raw record is never paywalled. Every\nrow carries a Fareseal document exactly as its site signed it — the\n`receipt` (kind=receipts) or `snapshot` (kind=reports) object, Ed25519\nover RFC 8785 JCS of that document minus `sig`, key = its own `site` —\nbeside a `","read_only":false},{"name":"tollbooth_sites","title":"","description":"Deprecated alias of fareseal_sites. Same data; use the /v1/fareseal/ path. Original description follows.\n\nMembership of the commons: every signing key that has reported, the\ndomain that vouched for it (by serving the key in its\n/.well-known/tollbooth-site.json), and when it was last re-checked.\nAttested only by default; tier=all adds unattested keys with the domain\nthey CLAIMED but that did not (y","read_only":false},{"name":"tollbooth_agents","title":"","description":"Deprecated alias of fareseal_agents. Same data; use the /v1/fareseal/ path. Original description follows.\n\nSpec 125, the agent conduct record. Every agent public key that an\nattested Fareseal site reported, with its summed request count,\nnewest first. Free, no auth, attested tier only. Facts, not verdicts:\nno score, no tier, no IP. Counts are a LOWER BOUND (an evicted entry or\na restarted isolate ","read_only":false},{"name":"tollbooth_agent_record","title":"","description":"Deprecated alias of agent_record. Served at /v1/fareseal/agents/{key}; same record.\n\nSpec 125. One agent public key's record across attested Fareseal\nsites: summed requests, a sample of paths, whether robots.txt was\nfetched, the signed snapshots each figure comes from (`sources[]`),\nand the newest 100 receipts naming the key, verbatim. Free, no auth.\nFacts, not verdicts: no score, no tier, no IP. ","read_only":false},{"name":"snapshot_manifest","title":"","description":"P4 corpus replication, the OPA \"push data into the PDP\" pattern. A\ndaily snapshot of the domain corpus (domain, score, category,\nfingerprinting, entity) is published as deterministic JSONL with a\nmanifest carrying row_count, sha256 over the exact bytes, a diff\nsummary vs the previous day, and an Ed25519-signed Receipt v1.0\ncommitted to the transparency log — a PDP that replicates the data\ncan veri","read_only":false},{"name":"snapshot_data","title":"","description":"The exact bytes the manifest's sha256 commits to. Content-Type\n`application/x-ndjson`; rows ordered by domain. Verify:\n`sha256(body) == manifest.sha256`.\n","read_only":false},{"name":"snapshot_diff","title":"","description":"JSONL diff vs the previous snapshot — apply +/~/- lines instead of re-pulling the corpus.","read_only":false},{"name":"status_history","title":"","description":"One sample per 20-minute monitor sweep. `uptime_pct` is the share of\nsweeps in which every fail point was green (the strictest read);\n`per_monitor` lists only monitors that failed at least once in the\nwindow. History begins at feature deploy and is never extrapolated\nbackwards — an empty window returns `uptime_pct: null`, not 100.\n","read_only":false},{"name":"get_self_view","title":"","description":"P83 Gate 1. The caller is the subject: every fact here comes from the\nTLS handshake and headers the caller has already sent, so there is no\nrender, no browser, and nothing to authorize.\n\nThree surfaces:\n- `client` — user-agent, HTTP protocol, TLS version/cipher, ClientHello\n  length, the pre-hashed JA3/JA4 input components, header order.\n- `state` — how many cookies were sent (never their values),","read_only":false},{"name":"agent_registries_lookup","title":"","description":"P75 registry aggregation: the cross-lens join applied to agent identity.\nIncumbent providers each consult only their own registry; this endpoint\nchecks every registry TunnelMind can reach and labels each answer with\nan explicit state, so a gap can never be mistaken for a clean result:\n\n- `observed` — the subject IS in this registry (record attached)\n- `not_present` — checked, and it isn't (an obse","read_only":false},{"name":"verify_agent","title":"","description":"Reconciles a claimed bot User-Agent against the operator's OWN published\nIP-range feed (Googlebot, GPTBot, OAI-SearchBot, ChatGPT-User,\nPerplexityBot, Perplexity-User, Bingbot). A User-Agent is trivial to\nforge; membership in the operator's published CIDR ranges is not. This\nexposes the common attack: a scraper sending `User-Agent: Googlebot` from\nan IP in none of Google's ranges.\n\nUse this tool w","read_only":false},{"name":"verify_agent_signature","title":"","description":"Neutral third-party Web Bot Auth verification. An origin — or the PDP\ndeciding for it — received a request from a claimed agent carrying the\nWeb Bot Auth headers (Signature, Signature-Input, Signature-Agent).\nRelay those headers here, plus the authority the request was addressed\nto, and TunnelMind verifies the Ed25519 signature against the agent's\nown published key directory\n(https://<agent>/.well","read_only":false},{"name":"create_subscription","title":"","description":"Subscribe to a node (ip, domain, asn, or entity slug). On a recurring\nsweep (~20 min) TunnelMind re-runs the fused `POST /v1/verify` verdict and,\nwhen the *material* result changes — the verdict label flips, the trust\nscore crosses a band, or the signal set changes — POSTs a signed event to\nyour `callback_url`.\n\nWebhook authenticity: every delivery carries an `X-TunnelMind-Signature:\nsha256=<hex>`","read_only":false},{"name":"list_subscriptions","title":"","description":"Returns the caller's active and inactive subscriptions (signing_key redacted). Requires an API key.","read_only":false},{"name":"get_subscription","title":"","description":"Read one of your subscriptions (signing_key redacted).","read_only":false},{"name":"delete_subscription","title":"","description":"Cancel a subscription.","read_only":false},{"name":"receipt_log_sth","title":"","description":"P72 RFC 6962 transparency log over the unified receipt ledger\n(ADR-010). The STH commits to the entire log: `tree_size`, `root_hash`\n(`0x` + SHA-256), `timestamp`, and an Ed25519 signature (with `key_id`\nand embedded public key) over the RFC 8785 canonicalization of the\nbody. Hashes only — receipt bodies are never on this surface.\n\nVerify offline with `scripts/verify-log.mjs sth` (zero TunnelMind\n","read_only":false},{"name":"receipt_log_inclusion_proof","title":"","description":"Proves a specific receipt (by unified `receipt_id`, lens alias, or raw\n`leaf_index`) is included in the tree at `tree_size` (default: the\nlatest STH's). Returns `leaf_hash`, the `audit_path`, the recomputed\n`root_hash`, and the matching STH. What this proves: the receipt in\nyour hand is byte-identical to the one sequenced into the log — not\nthat the observation inside it was correct (ADR-010).\n\nVe","read_only":false},{"name":"receipt_log_consistency_proof","title":"","description":"Proves the log at size `second` is an append-only extension of the log\nat size `first` — history was never rewritten. Returns both roots and\nthe proof path. Verify offline with\n`scripts/verify-log.mjs consistency <proof.json>`.\n\nWhere a signed tree head is stored at `first` or `second`, that root\nis checked against the current leaves; a mismatch (history rewritten\nsince the head was signed) answer","read_only":false},{"name":"receipt_lookup","title":"","description":"P72 unified receipt ledger (ADR-010): every receipt-issuing surface\n(cross-lens verify, tracker verify, verdict, profile, explain,\nGhostRoute, Sigil/ATAP, compliance export) records the exact signed\ndocument it returned, keyed by one ID space.\n\nUse this tool when:\n- An agent holds a receipt and wants to confirm TunnelMind logged it\n  (existence + canonical hash) before trusting it in an audit trai","read_only":false},{"name":"receipt_with_proof","title":"","description":"Spec 003 / ADR-044 decision 3. Returns the RFC 6962 inclusion proof\nfor one sequenced receipt against the latest Signed Tree Head, plus\nthe receipt itself where it may be shown.\n\nUse this tool when:\n- An agent found a receipt with `ledger_search` and wants to verify\n  it offline. The 2-call path: `ledger_search` (find the hit), then\n  `receipt_with_proof` (the receipt + inclusion proof + STH), the","read_only":false},{"name":"attributes_lookup","title":"","description":"P73 fast attributes endpoint (PIP-PLAN P3): a full `POST /v1/verify`\nresolve fans out across four lenses (~2s) — fine for preflight, fatal\ninside a per-request authorization loop. This endpoint serves the\nlast-known signed bundle from a single KV read, with the P69 freshness\ncontract deciding how much to trust it.\n\nUse this tool when:\n- A policy decision point (OPA, Cerbos, Cedar) needs node attri","read_only":false},{"name":"tracker_verify","title":"","description":"The Tracker lens-owned verify surface: a per-node verdict over the\nnormalized DDG Tracker Radar / IAB TCF / Disconnect.me corpus, with an\noptional signed TunnelMind Receipt v1.0. This is the single-lens ground\ntruth the fused `POST /v1/verify` cites for its tracker block.\n\nUse this tool when:\n- You need to know whether a domain is tracking/surveillance infrastructure\n  and which entity operates it","read_only":false},{"name":"sigil_verify_domain","title":"","description":"Confirms a publisher controls a domain by checking for a DNS TXT record\nthe owner publishes under `_tunnelmind.{domain}`. A DNS record can only\nbe set by whoever controls the zone, so its presence proves control — a\nstronger signal than ads.txt, which is just a file anything in the\nrequest path can serve.\n\nUse this tool when:\n- You want proof a publisher actually owns the domain it claims.\n- You a","read_only":false},{"name":"sigil_verify_ip_type","title":"","description":"Classifies an IPv4 or IPv6 address by network type — the high-value ad-fraud\nsignal being datacenter traffic posing as residential or living-room\n(CTV) devices. IP→ASN resolution uses Team Cymru's public service; the\nASN is then classified by its registered organization name.\n\nIt also cross-references the Scry attacker-observation corpus to detect\nanonymizing EGRESS — the thing a rotating-resident","read_only":false},{"name":"sigil_verify_adscert","title":"","description":"Reports whether a domain publishes ads.cert (IAB Tech Lab Authenticated\nConnections) DNS records — a readiness signal showing the domain\nsupports cryptographically authenticated ad-tech connections. This is\nnot signature verification: ads.cert is pairwise, so verifying a signed\nbid request requires Sigil to be a delegated participant (a future\nbuild). DNS-only and stateless.\n\nInputs:\n- `domain` (q","read_only":false},{"name":"sigil_verify_app_bundle","title":"","description":"Verifies that a mobile or CTV app bundle ID actually exists in the\nrelevant app store — used to detect bundle spoofing in bid requests.\n\nPlatform support (v1):\n- `ios`: verified live via Apple's iTunes Lookup API.\n- `android`: verified live via the Google Play store listing page.\n- `ctv_*` / `web`: no public store API — returns verified=null.\n\nInputs:\n- `bundle_id` (body, required): e.g. `com.nyti","read_only":false},{"name":"cross_lens_verify","title":"","description":"A2 — the cross-lens join. TunnelMind owns multiple halves of the\nopen-web graph: Scry sees who is on every IP (attacker intelligence,\nactor class, Augur threat-intel overlap); Sigil sees the supply graph\n(publishers, SSPs, DSPs, ads.txt + sellers.json + SupplyChain Object);\nGhostRoute sees routing integrity & sovereignty (RPKI origin validity,\nBGP prefix, claimed sovereign zone, sanctions, AI-infr","read_only":false},{"name":"cross_lens_lookup","title":"","description":"Returns all three lens views for a single node key without computing a\nfused verdict. Use this when you want raw transparency — the Tracker\ncatalog presence, Scry attacker observations, and Sigil supply-graph\nposition — and intend to make your own decision. For an opinionated\nverdict, call `cross_lens_verify` instead. For an agent-side\nallow/caution/deny gate plus signed consultation receipt, call","read_only":false},{"name":"verdict_lookup","title":"","description":"The reconciliation layer in one call. Where `cross_lens_verify` answers\n\"what is this network destination,\" `verdict_lookup` answers a different,\nsharper question about a key-addressed ACTOR: **does what this key claims\nabout itself match what the network has seen it do?**\n\nIt fuses two sides:\n- **claim** — what the key can prove about itself: its `attestation_tier`\n  across roots of trust (bare E","read_only":false},{"name":"preflight_should_i_act","title":"","description":"The single call an agent makes before transacting with a destination\non the open web. Composes the cross-lens verdict with a bounded\nTracker-presence bonus, maps the adjusted trust score to a tri-state\ndecision (`allow` / `caution` / `deny`), and returns a 5-minute signed\nconsultation receipt (`sigil_token` with `sub: preflight:consulted`).\n\nThe receipt is the load-bearing artifact: the agent atta","read_only":false},{"name":"explain_verdict","title":"","description":"Call this when you need to ACT ON a verdict and prove why. It returns the\nexact verdict `/v1/verify/{node}` computes (same fusion, same weights)\nPLUS a traced evidence chain: every claim is attributed to where it came\nfrom — the attested sensor fleet (with attestation tier), a named Augur\nthreat feed, sellers.json/ads.txt supply-graph presence, the cross-lens\nco-observation join, the DDG/IAB track","read_only":false},{"name":"profile_entity","title":"","description":"At least one of `ip`, `domain` or `entity` is required.\n\nCall this before routing traffic, bidding on inventory, or trusting a\ncounterparty. It fuses ALL THREE TunnelMind lenses for one subject —\nScry (attacker intelligence + threat feeds + open ports), Sigil\n(ad-supply-chain position + trust score + ATAP witness count), and\nTracker (DDG/IAB catalog + prevalence + categories) — into a single\nconfi","read_only":false},{"name":"signal_tracker_density","title":"","description":"Observed component counts first, a labelled derived roll-up second. The\ncomponents — `data_categories`, supply-surface counts (ssp + publisher +\ndsp + owns_seat + buys_through), and corroborating `sources` — are facts.\n`derived.tracker_density` (0–100) is a weighted blend of those counts, not\na measurement; `data_cost_usd` is deliberately excluded (non-zero only for\na curated seed, so weighting by","read_only":false},{"name":"signal_dark_pool_risk","title":"","description":"Reconciles every sell path a publisher declares (`sells_through`) against\neach SSP's own sellers.json (`exchange_seat`) and keeps three classes\nstrictly separate: `corroborated` (seat present), `contradicted` (SSP\ncrawled but seller_id absent — real risk), and `unchecked` (SSP not yet\ncrawled — excluded from risk, lowers confidence). Combined with\npublisher-side ads.txt opacity. Two-sided corrobor","read_only":false},{"name":"signal_halo_score","title":"","description":"Scores an entity by the trust character of its neighbours — the SSPs its\npublishers sell through and the DSPs it buys through. Reports neighbour\ncounts, mean/min neighbour trust, and how many neighbours are\nadversary-classified (P46). `derived.halo_score` (0–100, or null when no\nneighbour has a computed trust) is mean neighbour trust dragged down by\nadversary-neighbour share. Evidence about an ent","read_only":false},{"name":"signal_team_signal","title":"","description":"Surfaces other entities that operate as a coordinated team with this one:\nthey share a NARROWLY-held direct seller account (2–8 entities — network\nhouse accounts shared by hundreds are separated into\n`house_accounts_excluded`, not counted) or co-own an exchange seat.\n`derived.team_signal` (0–100) is a coordination magnitude over teammate\ncount, shared-account breadth, and co-owned seats.\n","read_only":false},{"name":"sigil_verify_supply_path","title":"","description":"The core Sigil pre-bid call. Submit a supply path; Sigil composes its\nindividual checks into one trust verdict and returns a signed\n`sigil_token` the agent can attach to its bid as proof of verification.\n\nChecks composed:\n- `ads_txt` — exchange authorized in the publisher's ads.txt.\n- `datacenter_ip` — is the IP a datacenter posing as a real user.\n- `fraud_signals` — is the IP in Scry's attacker-i","read_only":false},{"name":"sigil_verify_token","title":"","description":"Verifies the authenticity and expiry of a `sigil_token` returned by\n`sigil_verify_supply_path`. Anyone can call this — no key needed; Sigil\nverifies the Ed25519 signature server-side. Tokens live 5 minutes.\n\nReturns `valid` (boolean), `reason` (when invalid: malformed / expired /\nbad_signature / unsigned), and the decoded `payload`.\n","read_only":false},{"name":"sigil_verify_supply_chain","title":"","description":"The bid-time contract. Pass the SupplyChain object from an OpenRTB bid\nrequest (`source.ext.schain`) verbatim, plus the originating site domain\nor app bundle. Sigil verifies, per node and in aggregate:\n\n- origin ads.txt — the publisher's ads.txt authorizes node[0] (asi + sid).\n- per node — the node's `asi` sellers.json declares the node's `sid`.\n- owner-domain — node[0]'s sellers.json seller `doma","read_only":false},{"name":"sigil_traverse","title":"","description":"Reconstructs the supply paths for a publisher domain from Sigil's own\ncrawl and returns them ITEMIZED — distinct from `sigil_verify_supply_chain`\n(which verifies a schain the caller brings) and from `signal_dark_pool_risk`\n(which returns only aggregate counts). Every SSP the publisher declares it\nsells through is joined to that SSP's identity and classified two-sided\nagainst the SSP's sellers.json","read_only":false},{"name":"get_stats","title":"","description":"One public \"state of the corpus\" readout — the whole graph in a single\ncall. Distinct from the Scry-only sensor stats at\napi.tunnelmind.ai/v1/stats (which this reuses for the `scry` block): this\nspans Scry, Sigil, and Tracker plus the attestation and routing layers.\n\nUse it to cite live coverage — how many publishers / SSPs / DSPs / sell\npaths / sellers.json seats are in the Sigil supply graph, ho","read_only":false},{"name":"get_website_history","title":"","description":"The over-time layer behind the site's website map (the successor to\nthe retired radar). Every domain verify appends the domain's machinery tuple\n— origin AS, RPKI state, announced prefix, network country, CDN,\ncertificate authority, registrar, owning entity, and the per-lens\ncoverage tri-states — to an append-only change-log, one row per\nobserved change (plus a daily heartbeat row per looked-up do","read_only":false},{"name":"get_freshness","title":"","description":"D4 — the freshness contract a PDP can gate on. For each lens (Scry /\nSigil / Tracker / GhostRoute) this reports the newest observation\ntimestamp in the corpus, the declared ingest cadence (taken from the\ningester's own code and cron schedules, never asserted), the published\nSLO, the current corpus age in seconds, and whether the SLO holds.\nGhostRoute reports its three corpus workers (CT hourly, RP","read_only":false},{"name":"get_tool_registry","title":"","description":"Spec 097 FR-010 / ADR-034. Returns the tool registry generated from\nopenapi.yaml: one entry per operation with its version, status\n(active / deprecated / retired), lens and schema hash, plus the\n`registry_hash` over the whole set. Retired entries stay listed.\nNo database read: the registry is compiled into the running Worker.\n\nFreshness: `observed_at` is the response time, `valid_until` is 24 hour","read_only":false},{"name":"get_pricing","title":"","description":"Spec 097 / ADR-035 Amendment C8. Returns the usage-tiered price schedule\nfor paid calls. Prices are integer strings of USDC atomic units\n(6 decimals). Rows are `{tier, from, to, price_atomic}`; `to` is null for\nthe open tier. `anonymous` is the price a call without an API key pays.\nThe schedule is the compiled-in default unless a validated override is held\nin KV (one KV read, no database read); `s","read_only":false},{"name":"get_demand_aggregate","title":"","description":"Weekly public aggregate of demand: what callers asked this API for that it\ndid not have or rejected (ghost routes, rejected arguments, ghost MCP tools, tools/list counts). One ISO week, Monday 00:00 UTC to the next Monday\n00:00 UTC (`?week=` picks the week containing a date; default is the current\nweek). Aggregate rows only: a row is published only when at least\n`n_threshold` (3) distinct actors p","read_only":false},{"name":"get_changes","title":"","description":"The change ledger, read back: what TunnelMind itself changed in the window,\nnewest first, as one Ed25519-signed document.\n\nUse this tool when:\n- you need to know what changed in TunnelMind's site, prices, tools or operations, and want it signed rather than asserted.\n- you are checking whether a tool or price you rely on moved recently.\n\nItems come from receipts with lens `config`: the five recorde","read_only":false},{"name":"ledger_search","title":"","description":"One public search over the receipt sources, newest first. Not `/v1/search`\n(that is the domain search).\n\nUse this tool when:\n- you want to find a TunnelMind change by ref, kind or summary.\n- you want one newest-first view of TunnelMind's changes and the attested Fareseal commons.\n- you want a past day's signed station-health rows (`source=weather-health`).\n- you want the roster of attested agent k","read_only":false}],"server_info":{"name":"tunnelmind-data-api","version":"1.0.0"},"category":"agents","tags":["cloud","productivity","web-search"],"kind":"remote","source":"registry","submitted":{},"first_party":true,"domain_rank":null,"score":100,"indexable":true,"first_seen":"2026-08-03","stars":0,"badges":[],"sponsor":null,"page":"https://agentsindex.org/agents/ai-tunnelmind-data/"}