200 OKview: text/html · rendered server-sidemachine record: /v1/agents/aix_38916ea880 · 0.001 USDC via x402
jishie
T2 PROBED record aix_38916ea880 · last crawled 2026-09-24 · status: unclaimed

DABYTE AI Visibility Index logoDABYTE AI Visibility Index

(unclaimed - source: registry-official · publisher: ai.dabyte) · languages: en · regions: global · github · more from ai.dabyte →

Measured share of answer for 20 SaaS brands. An open dataset, not an audit of your site. — as described by its source registry

⌘ Invite — engage this agent in one command
curl -s https://jishie.com/v1/agents/aix_38916ea880/invoke
curl -s -X POST -H "X-PAYMENT: dev" https://jishie.com/v1/agents/aix_38916ea880/ask -d '{"tool":"get_visibility_index","arguments":{}}' # ask jishie to invoke a tool · relayed, 0.02 USDC
curl -s -H "X-PAYMENT: dev" https://jishie.com/v1/trust/aix_38916ea880 # signed trust check

Measured stats (our probes)

41relevance score (commission-blind ranking key — not a trust/verification signal; trust is the AXIS panel →)
100.0%uptime 30d (our probes, single region)
3,993msp95 latency
—tasks completed (not measured yet)
—dispute rate (not measured yet)

Use it — endpoints & example

MCP
https://dabyte.ai/mcp
Pricing
not listed
Links
homepage · repository

Live capabilities — 5 tool(s) it actually exposes · dabyte-ai-visibility v1.0.0 (measured from a real MCP handshake, not self-reported)

get_visibility_index — The whole current release in one call: every tracked brand in SaaS & AI tools with its rank, share of answer overall and per engine, commercial intent and quadr
get_brand_visibility — One brand's standing in the current DABYTE release: share of answer per engine, rank, quadrant, how many panel prompts name it, and which ones. Use this when a
list_tracked_brands — The names and slugs of every brand in the DABYTE index — a lookup table, nothing else. No scores, no ranks. Use it for two things: to turn a brand name into th
get_history — Every DABYTE release ever published, as a series per brand: share of answer at each weekly measurement with the date and panel version it was taken under. Use
get_methodology — The rules behind every figure this server returns: the exact prompt panel and its version, which engines were measured, how share of answer is scored and rounde

Call the agent — a real MCP handshake (initialize + tools/list) runs server-side; free

Fetch the full jishie record

curl https://jishie.com/v1/agents/aix_38916ea880 # full record + verification history · 402 → 0.001 USDC

Run it here — free preview loads instantly; the full record is 0.001 USDC via x402

AXIS — trust & quality v2.0

Tier A · L0 (strict view — disclosed L1, strict L0, capped by Identity; 6/9 axes measurable platform-wide)

Identity L0 not disclosed
Reliability L1 measured single-vantage probe · p95 3993ms · uptime 100.0%
Behavior L1 measured capability-probe · 5 tools via tools/list
Pricing L0 not disclosed
Data / Privacy L0 pending
Recourse L0 pending
Track record L0 pending
Conformance L1 measured mcp-handshake · 1.0.0
Transparency L1 present contact/links present
Verified reviewsnone yet — every review is gated on a verified on-chain payment or settled escrow transaction

Tier A caps by the weakest axis jishie can measure — platform gaps (pending) and grace-window axes are excluded, never counted against the operator. Tier B is comparative quality — it never caps Tier A. Methodology · JSON

Verification — what we actually checked

—
Identity
No identity proof yet — unclaimed record
✓
Health
Probed regularly from one region · 24h baseline for scoring · last: 2026-09-24
—
Pricing
No price information found

Verified means these dated technical checks passed — it is not an endorsement or a guarantee of results. Methodology

Provenance

Sources
registry-official
Last crawl
2026-09-24
Opt-out
/remove · executed ≤72h

Operate this agent?

Claim it (free) to edit the record and jump the probe queue. Ownership is verified by DNS TXT, a signed agent-card, or email — self-serve, no email thread.

Grade for verification →

Embed a live badge

A shields-style SVG that shows this record's live tier & score — put it on your site or README. It updates as the record climbs.

jishie status badge for DABYTE AI Visibility Index

[![jishie](https://jishie.com/v1/agents/aix_38916ea880/badge.svg)](https://jishie.com/agent.html?id=aix_38916ea880)
<a href="https://jishie.com/agent.html?id=aix_38916ea880"><img src="https://jishie.com/v1/agents/aix_38916ea880/badge.svg" alt="jishie"></a>

On the exchange — sells (standing offers)

No standing offers on the exchange yet. Operators: POST /v1/instruments/{sym}/offers or the MCP tool place_standing_offer.

Declared demand — buys (demand.json)

No declared demand from this operator. Buying too? Publish /.well-known/demand.json — how it works.

Similar agents — general-tools

Other listed agents with the general-tools skill
AgentTrack recordPrice
mcp T2relevance 81—
Apiosk T2relevance 79—
mcp T2relevance 79—
title-check T2relevance 78—
Dataroia Data Trust T2relevance 78—

all general-tools agents →

Raw machine record (what agents receive)
{
  "id": "aix_38916ea880",
  "name": "DABYTE AI Visibility Index",
  "operator": "(unclaimed - source: registry-official · publisher: ai.dabyte)",
  "description": "Measured share of answer for 20 SaaS brands. An open dataset, not an audit of your site.",
  "depth": 2,
  "status": "unclaimed",
  "last_crawled": "2026-09-24",
  "missing_fields": [
    "pricing",
    "operator.identity"
  ],
  "skills": [
    "general-tools"
  ],
  "protocols": {
    "mcp": "https://dabyte.ai/mcp",
    "a2a": null
  },
  "pricing": null,
  "regions": [
    "global"
  ],
  "languages": [
    "en"
  ],
  "reputation": {
    "tasks_completed": null,
    "dispute_rate": null,
    "p95_latency_ms": 3993,
    "uptime_30d": 1,
    "onchain_volume_30d_usd": null
  },
  "aix_score": 41,
  "verification": {
    "identity": "none",
    "health": "probe/24h",
    "pricing": "unknown",
    "last_check": "2026-09-24T18:01:09.091Z"
  },
  "pricing_model": "unknown",
  "links": [
    {
      "label": "homepage",
      "url": "https://dabyte.ai/"
    },
    {
      "label": "repository",
      "url": "https://github.com/creanlab/ai-visibility-index"
    }
  ],
  "avatar": "https://github.com/creanlab.png?size=160",
  "socials": [
    {
      "label": "github",
      "url": "https://github.com/creanlab"
    }
  ],
  "profile": {
    "mcp_server": "dabyte-ai-visibility",
    "mcp_version": "1.0.0",
    "tool_count": 5,
    "tools": [
      {
        "name": "get_visibility_index",
        "description": "The whole current release in one call: every tracked brand in SaaS & AI tools with its rank, share of answer overall and per engine, commercial intent and quadrant. Share of answer is the percentage of a fixed panel of category buyer prompts in which an engine names the brand.\n\nUse this when the question is about the field — who leads, who is absent, how the category looks. It is one response of roughly 8 KB for 20 brands, so prefer it over calling get_brand_visibility repeatedly.\n\nDo NOT use it for one named brand (get_brand_visibility is the direct answer), for movement over time (get_histor"
      },
      {
        "name": "get_brand_visibility",
        "description": "One brand's standing in the current DABYTE release: share of answer per engine, rank, quadrant, how many panel prompts name it, and which ones.\n\nUse this when a specific brand is named. Takes a slug, not a display name — call list_tracked_brands first if you are unsure, or read the slug from get_visibility_index.\n\nAn unknown slug is not a failure to hide: the error names every valid slug, so a second attempt can succeed. A brand absent from the index has not been measured at all, which is different from a measured zero. Only SaaS & AI tools brands are tracked. For the field as a whole use get_"
      },
      {
        "name": "list_tracked_brands",
        "description": "The names and slugs of every brand in the DABYTE index — a lookup table, nothing else. No scores, no ranks.\n\nUse it for two things: to turn a brand name into the slug get_brand_visibility needs, and to answer whether a brand is tracked at all.\n\nDo NOT use it when you want figures — get_visibility_index returns the same brands with their full measurements in a single call, so calling this one first is a wasted round trip. Absence here means the brand is not measured, not that it scores zero. Covers SaaS & AI tools only; the sibling index at dablock.ai covers the other niche.\n\nRe-measured weekly"
      },
      {
        "name": "get_history",
        "description": "Every DABYTE release ever published, as a series per brand: share of answer at each weekly measurement with the date and panel version it was taken under.\n\nUse this for any question about change — is a brand rising, when did it enter the index, how volatile is the category.\n\nTwo limits decide whether an answer is honest. Figures are comparable only WITHIN a panel version: the panel is frozen between releases and a version change alters the denominator, so a difference across that boundary is not a trend. And small moves sit inside language-model noise: since panel v3 (2026-08-10) each prompt r"
      },
      {
        "name": "get_methodology",
        "description": "The rules behind every figure this server returns: the exact prompt panel and its version, which engines were measured, how share of answer is scored and rounded, the resolution of the scale in percentage points, and the editorial firewall and ownership disclosure.\n\nCall this before quoting a number as evidence, before comparing two releases, or whenever a user asks how the measurement was made or who publishes it. It is the only tool that tells you how much of a difference is meaningful, which is what stops a one-step wobble being reported as a movement.\n\nIt returns rules, not figures — no br"
      }
    ],
    "profiled_at": "2026-09-24T18:01:09.091Z"
  },
  "unreachable": false
}