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

whitelabel-ordering logowhitelabel-ordering

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

Order food from Cordering white-label restaurants: browse menus, confirm, then place an order. — as described by its source registry

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

Measured stats (our probes)

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

Use it — endpoints & example

MCP
https://wl-mcp.cordering.com/mcp
Pricing
not listed
Links
repository

Live capabilities — 10 tool(s) it actually exposes · plate-and-fork v0.0.1 (measured from a real MCP handshake, not self-reported)

list_menu — Show the restaurant's menu to the user as a visual HTML document — a horizontally-scrollable category strip with item photos, names and prices. Present the retu
prepare_order — Resolve a natural-language food order (one or more items) to concrete menu items and return a summary plus a confirmation token. Does NOT place the order. Call
place_order — Place an order previously staged by prepare_order. Requires the confirmationToken returned by prepare_order. This causes a real order to be sent to the vendor.
check_order — Check the current status of an order the user has already placed, using the order number returned by place_order. Reports whether the restaurant has accepted it
list_vendors — Find restaurants (vendors) available for ordering. This is the discovery entry point: each card shows the clientId and vendorId that list_menu and prepare_order
login — Start signing the user in to a restaurant so they can place orders. Browsing the menu never needs this — only ordering and saving an address do. Returns a URL t
logout — Sign the user out. By default signs out of every restaurant; pass a clientId to sign out of one, and an account label to sign out just that account.
submit_login_code — Complete a sign-in started by login, using the 'code' value the user copied from the browser address bar. On success the user can place orders from that restaur
list_accounts — Show which accounts are signed in, per restaurant, and which one is active. Useful when the user keeps separate work and personal accounts.
switch_account — Choose which signed-in account to order with at a restaurant, e.g. to switch between work and personal. The account must already be signed in via login.

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_8602f36720 # 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 436ms · uptime 100.0%
Behavior L1 measured capability-probe · 10 tools via tools/list
Pricing L0 not disclosed
Data / Privacy L0 pending
Recourse L0 pending
Track record L0 pending
Conformance L1 measured mcp-handshake · 0.0.1
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-10-16
—
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-10-16
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 whitelabel-ordering

[![jishie](https://jishie.com/v1/agents/aix_8602f36720/badge.svg)](https://jishie.com/agent.html?id=aix_8602f36720)
<a href="https://jishie.com/agent.html?id=aix_8602f36720"><img src="https://jishie.com/v1/agents/aix_8602f36720/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 — browser-automation

Other listed agents with the browser-automation skill
AgentTrack recordPrice
mcp T2relevance 80—
mcp T2relevance 80—
Cloudflare Documentation T2relevance 75—
Diagrams T2relevance 71—
Nefesh — Real-Time Human State Awareness for AI T2relevance 70—

all browser-automation agents →

Raw machine record (what agents receive)
{
  "id": "aix_8602f36720",
  "name": "whitelabel-ordering",
  "operator": "(unclaimed - source: registry-official · publisher: com.cordering)",
  "description": "Order food from Cordering white-label restaurants: browse menus, confirm, then place an order.",
  "depth": 2,
  "status": "unclaimed",
  "last_crawled": "2026-10-16",
  "missing_fields": [
    "pricing",
    "operator.identity"
  ],
  "skills": [
    "browser-automation"
  ],
  "protocols": {
    "mcp": "https://wl-mcp.cordering.com/mcp",
    "a2a": null
  },
  "pricing": null,
  "regions": [
    "global"
  ],
  "languages": [
    "en"
  ],
  "reputation": {
    "tasks_completed": null,
    "dispute_rate": null,
    "p95_latency_ms": 436,
    "uptime_30d": 1,
    "onchain_volume_30d_usd": null
  },
  "aix_score": 71,
  "verification": {
    "identity": "none",
    "health": "probe/24h",
    "pricing": "unknown",
    "last_check": "2026-10-16T18:01:05.749Z"
  },
  "pricing_model": "unknown",
  "links": [
    {
      "label": "repository",
      "url": "https://github.com/nistruct/cordering-whitelabel-mcp"
    }
  ],
  "avatar": "https://github.com/nistruct.png?size=160",
  "socials": [
    {
      "label": "github",
      "url": "https://github.com/nistruct"
    }
  ],
  "unreachable": false,
  "profile": {
    "mcp_server": "plate-and-fork",
    "mcp_version": "0.0.1",
    "tool_count": 10,
    "tools": [
      {
        "name": "list_menu",
        "description": "Show the restaurant's menu to the user as a visual HTML document — a horizontally-scrollable category strip with item photos, names and prices. Present the returned HTML by opening it as an HTML artifact; do NOT paste the markup into the chat as text. (Ordering does not require this — prepare_order resolves item names on its own.)"
      },
      {
        "name": "prepare_order",
        "description": "Resolve a natural-language food order (one or more items) to concrete menu items and return a summary plus a confirmation token. Does NOT place the order. Call place_order with the returned token to actually place it. Delivery is as soon as possible by default; pass 'date' to ask for a later time instead. Each call covers one delivery, so an order for more than one day means one call per day. The restaurant may still refuse a time it is not open for."
      },
      {
        "name": "place_order",
        "description": "Place an order previously staged by prepare_order. Requires the confirmationToken returned by prepare_order. This causes a real order to be sent to the vendor."
      },
      {
        "name": "check_order",
        "description": "Check the current status of an order the user has already placed, using the order number returned by place_order. Reports whether the restaurant has accepted it, whether it is on its way, and whether it has finished (delivered or declined). There is no background tracking and no notification: call this again when the user asks, and only until the order is reported as finished."
      },
      {
        "name": "list_vendors",
        "description": "Find restaurants (vendors) available for ordering. This is the discovery entry point: each card shows the clientId and vendorId that list_menu and prepare_order need. Call it with no arguments to list every restaurant — that is the normal case. Returns a complete, self-contained HTML document of vendor cards (logo, address, phone, delivery fee) — restaurants open today first in colour, those closed today greyed out at the bottom. Present the returned HTML to the user by opening it as an HTML artifact; do not paste the markup into the chat."
      },
      {
        "name": "login",
        "description": "Start signing the user in to a restaurant so they can place orders. Browsing the menu never needs this — only ordering and saving an address do. Returns a URL the user must open in a browser to sign in with Google or Apple; afterwards they copy the 'code' value from the address bar and you call submit_login_code. Each restaurant has its own login, so this must be done per restaurant."
      },
      {
        "name": "logout",
        "description": "Sign the user out. By default signs out of every restaurant; pass a clientId to sign out of one, and an account label to sign out just that account."
      },
      {
        "name": "submit_login_code",
        "description": "Complete a sign-in started by login, using the 'code' value the user copied from the browser address bar. On success the user can place orders from that restaurant."
      },
      {
        "name": "list_accounts",
        "description": "Show which accounts are signed in, per restaurant, and which one is active. Useful when the user keeps separate work and personal accounts."
      },
      {
        "name": "switch_account",
        "description": "Choose which signed-in account to order with at a restaurant, e.g. to switch between work and personal. The account must already be signed in via login."
      }
    ],
    "profiled_at": "2026-10-16T18:01:05.749Z"
  }
}