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

listing logolisting

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

List on MLS, sell, show, compare and close your real estate property on beycome. — as described by its source registry

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

Measured stats (our probes)

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

Use it — endpoints & example

MCP
https://mcp.beycome.com/mcp
Pricing
not listed
Links
homepage · repository

Live capabilities — 14 tool(s) it actually exposes · com.beycome/listing v1.0.0 (measured from a real MCP handshake, not self-reported)

beycome_signup — Account stage — register a new beycome user (POST /auth/register). Use when the owner has no account yet. beycome is passwordless: registering automatically em
beycome_signin_start — Account stage — send a one-time sign-in code (POST /auth/check-email). beycome is passwordless — never ask the user for a password. This emails the user a 6-di
beycome_signin_verify — Account stage — exchange the one-time code for the access_token (POST /auth/validate-code). The gateway to the listing flow. Call after `beycome_signin_start`
beycome_check_coverage — Discovery stage — is this state served by beycome MLS? (GET /mls/is-covered). No account or prop_id needed. Use before listing to confirm beycome operates in t
beycome_estimate — Discovery stage — estimate a property's SALE value (beycome CMA + Zillow Zestimate). No account or prop_id needed. Returns both estimates plus suggested pricin
beycome_rental_estimate — Discovery stage — estimate a property's monthly RENT (POST /gemini-estimate). No account or prop_id needed. Pairs with `beycome_estimate`, but this tool is SPE
beycome_comps — Discovery stage — sold comparable listings near a location (GET /comps). No account or prop_id needed. Supports price / beds / baths / area / lot / type filter
beycome_questionnaire_link — Questionnaire stage — mint a pre-authorized link to the MLS questionnaire form (POST /api/mls/questionnaire-link). Requires a PAID listing (premium active, Fla
beycome_submit_property_link — Listing-creation stage — mint a pre-authorized link to the submit-property page (POST /api/mls/submit-property-link). Call AFTER signing in (`beycome_signin_ve
beycome_get_my_listings — Recovery stage — the signed-in user's properties (GET /properties). Token-scoped RESO list endpoint on the normal api base. Two main uses: - After the user f
beycome_offers — Post-publish stage — offers received on the owner's listings (GET /offers). Used once a listing is live. Requires ``access_token``. Returns a paginated list (2
beycome_showings — Post-publish stage — calendar of showings, open houses, and offer deadlines (GET /calendar/events). Used once a listing is live. The API requires the date rang
beycome_messages — Post-publish stage — read the owner's buyer/inquiry messages (GET /messages). Read-only. Requires ``access_token``. Two modes: - Omit ``thread`` → lists the
beycome_reply_message — Post-publish stage — reply to a buyer/inquiry message (POST /messages/reply). Sends a real message and queues a real email notification to the recipient, so th

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_65a62e0f2d # 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 1524ms · uptime 100.0%
Behavior L1 measured capability-probe · 14 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 listing

[![jishie](https://jishie.com/v1/agents/aix_65a62e0f2d/badge.svg)](https://jishie.com/agent.html?id=aix_65a62e0f2d)
<a href="https://jishie.com/agent.html?id=aix_65a62e0f2d"><img src="https://jishie.com/v1/agents/aix_65a62e0f2d/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
AgentsCoin T2relevance 80—
Cloudflare Documentation T2relevance 78—
mcp T2relevance 74—
mcp T2relevance 73—
mcp T2relevance 73—

all browser-automation agents →

Raw machine record (what agents receive)
{
  "id": "aix_65a62e0f2d",
  "name": "listing",
  "operator": "(unclaimed - source: registry-official · publisher: com.beycome)",
  "description": "List on MLS, sell, show, compare and close your real estate property on beycome.",
  "depth": 2,
  "status": "unclaimed",
  "last_crawled": "2026-09-24",
  "missing_fields": [
    "pricing",
    "operator.identity"
  ],
  "skills": [
    "browser-automation",
    "calendar-sync"
  ],
  "protocols": {
    "mcp": "https://mcp.beycome.com/mcp",
    "a2a": null
  },
  "pricing": null,
  "regions": [
    "global"
  ],
  "languages": [
    "en"
  ],
  "reputation": {
    "tasks_completed": null,
    "dispute_rate": null,
    "p95_latency_ms": 1524,
    "uptime_30d": 1,
    "onchain_volume_30d_usd": null
  },
  "aix_score": 52,
  "verification": {
    "identity": "none",
    "health": "probe/24h",
    "pricing": "unknown",
    "last_check": "2026-09-24T22:00:43.892Z"
  },
  "pricing_model": "unknown",
  "links": [
    {
      "label": "homepage",
      "url": "https://www.beycome.com/"
    },
    {
      "label": "repository",
      "url": "https://github.com/beycome/mcp.beycome.com"
    }
  ],
  "avatar": "https://github.com/beycome.png?size=160",
  "socials": [
    {
      "label": "github",
      "url": "https://github.com/beycome"
    }
  ],
  "profile": {
    "mcp_server": "com.beycome/listing",
    "mcp_version": "1.0.0",
    "tool_count": 14,
    "tools": [
      {
        "name": "beycome_signup",
        "description": "Account stage — register a new beycome user (POST /auth/register).\n\nUse when the owner has no account yet. beycome is passwordless: registering\nautomatically emails the user a 6-digit sign-in code, so the next step is\n`beycome_signin_verify` with that code — do NOT call `beycome_signin_start`\nafter signup, the code is already on its way. If the email is already\nregistered, this still just sends a sign-in code (signup doubles as\nsignin-start). Requires ``firstname`` and ``phone``; validation errors come\nback as HTTP 400 with an ``errors`` array. No prop_id needed."
      },
      {
        "name": "beycome_signin_start",
        "description": "Account stage — send a one-time sign-in code (POST /auth/check-email).\n\nbeycome is passwordless — never ask the user for a password. This emails the\nuser a 6-digit code (a second, different code also goes out by SMS; either\none works). Ask the user for the code they received, then exchange it for\nthe access_token with `beycome_signin_verify`.\n\nRead the response body, not the HTTP status — the envelope's ``ok`` mirrors\nthe HTTP status, and auth failures here still return 2xx. Always check\n``data.success``:\n  - ``success: true`` (201, \"Email sent\") — code sent; ask the user for it.\n  - ``success"
      },
      {
        "name": "beycome_signin_verify",
        "description": "Account stage — exchange the one-time code for the access_token (POST /auth/validate-code).\n\nThe gateway to the listing flow. Call after `beycome_signin_start` or\n`beycome_signup` (both send the code) with the 6-digit code the user\nreceived. On success the Bearer token is at ``data.data.access_token``\n(``expires_in`` gives its lifetime in seconds — tokens are long-lived, so\nmid-session expiry is rare). Pass it as ``access_token`` to every\nauthenticated tool: `beycome_submit_property_link`, `beycome_get_my_listings`,\n`beycome_questionnaire_link`, `beycome_offers`, `beycome_showings`,\n`beycome_m"
      },
      {
        "name": "beycome_check_coverage",
        "description": "Discovery stage — is this state served by beycome MLS? (GET /mls/is-covered).\n\nNo account or prop_id needed. Use before listing to confirm beycome operates\nin the property's state; ``is_active: true`` means covered. If not covered,\nthe listing flow does not apply."
      },
      {
        "name": "beycome_estimate",
        "description": "Discovery stage — estimate a property's SALE value (beycome CMA + Zillow Zestimate).\n\nNo account or prop_id needed. Returns both estimates plus suggested pricing\nstrategies (fast / balanced / max). Use during discovery to set a list price;\npair with `beycome_comps`. For rental inquiries, use `beycome_rental_estimate` instead."
      },
      {
        "name": "beycome_rental_estimate",
        "description": "Discovery stage — estimate a property's monthly RENT (POST /gemini-estimate).\n\nNo account or prop_id needed. Pairs with `beycome_estimate`, but this tool\nis SPECIFICALLY for rental estimates: use it ONLY for rental inquiries or\nfor properties that have a unit number. For sale-price estimates, use\n`beycome_estimate`.\n\nReturns ``rentEstimate`` (e.g. \"$2,600\"), ``rentEstimateRange`` (e.g.\n\"$2,400 - $2,800\"), and the ``sources`` the figure was grounded on (source\nURLs are stripped to keep the response small).\n\nCaveat: an unrecognized address still returns ``success: true`` with a\ngeneric market-av"
      },
      {
        "name": "beycome_comps",
        "description": "Discovery stage — sold comparable listings near a location (GET /comps).\n\nNo account or prop_id needed. Supports price / beds / baths / area / lot /\ntype filters. Use during discovery to support pricing alongside\n`beycome_estimate`.\n\nSlow endpoint: a cold query can take up to ~1 minute to respond — this is\nnormal, you can always retry the call if it times out. Photo URL and\nlisting-link fields are stripped from the records to keep the response\nsmall."
      },
      {
        "name": "beycome_questionnaire_link",
        "description": "Questionnaire stage — mint a pre-authorized link to the MLS questionnaire form (POST /api/mls/questionnaire-link).\n\nRequires a PAID listing (premium active, Flat/Yes) — whether the user just\npaid on the submit-property page (`beycome_submit_property_link`) or\nalready had a paid listing with the questionnaire still pending. Returns a pre-authorized link (expires in 7 days) — this tool\nonly hands back the URL; everything else happens in the browser, with no\nlogin step. Present the URL and tell the user that on the page they will:\n  1. review the pre-filled MLS questionnaire and complete any fiel"
      },
      {
        "name": "beycome_submit_property_link",
        "description": "Listing-creation stage — mint a pre-authorized link to the submit-property page (POST /api/mls/submit-property-link).\n\nCall AFTER signing in (`beycome_signin_verify`). User-scoped — no prop_id\nexists yet. Returns a\npre-authorized link (expires in 7 days) — this tool only hands back the URL;\nthe listing is created in the browser, with no login step. Present the URL\nand tell the user that on the page they will:\n  1. fill out their property's information,\n  2. set a price,\n  3. choose a package and any add-ons,\n  4. pay.\nTell them to return to the chat once payment is complete.\n\nPrefill: the page"
      },
      {
        "name": "beycome_get_my_listings",
        "description": "Recovery stage — the signed-in user's properties (GET /properties).\n\nToken-scoped RESO list endpoint on the normal api base. Two main uses:\n  - After the user finishes the submit-property page\n    (`beycome_submit_property_link`): find the newly created listing\n    (typically the newest entry), CONFIRM the address with the user, then\n    use its id as ``prop_id`` for `beycome_questionnaire_link`.\n  - As the entry point for a returning user who already has listings (or\n    references \"my listing\" without an id): locate the listing and read its\n    status to pick the next step — paid but questio"
      },
      {
        "name": "beycome_offers",
        "description": "Post-publish stage — offers received on the owner's listings (GET /offers).\n\nUsed once a listing is live. Requires ``access_token``. Returns a paginated\nlist (20 per page; pass ``page`` to advance) of every offer across all of the\nsigned-in user's listings — each entry is the full offer record (buyer,\nprice, contingencies, dates, status). Read-only.\n\nThere is no server-side ``prop_id`` filter; to show offers for one listing,\nfilter client-side on each offer's ``prop_id``. Responding to an offer\n(accept / reject / counter) is not exposed here."
      },
      {
        "name": "beycome_showings",
        "description": "Post-publish stage — calendar of showings, open houses, and offer deadlines (GET /calendar/events).\n\nUsed once a listing is live. The API requires the date range, so it defaults\nto today → +90 days when omitted (``from_date`` / ``to_date`` are\n``YYYY-MM-DD``, with ``to_date`` on or after ``from_date``). ``prop_id``\nfilters to one listing; omit it for every listing the user owns.\n\nThe response always mixes ALL event kinds — each event carries a ``type``\nfield (``showing`` / ``open_house`` / ``offer``). There is no server-side\ntype filter; when the user asks for one kind, filter on that field yo"
      },
      {
        "name": "beycome_messages",
        "description": "Post-publish stage — read the owner's buyer/inquiry messages (GET /messages).\n\nRead-only. Requires ``access_token``. Two modes:\n  - Omit ``thread`` → lists the ~20 most recent conversations, newest first,\n    one row per thread (the latest message in each). Useful fields per row:\n    ``address``, ``prop_id``, ``prop_status``, ``msg`` (latest text),\n    ``subject``, ``requested_by`` / ``email`` (the other party), ``thread``,\n    ``read_msg`` (\"0\" = unread), ``attachments``, and ``message_type``\n    (``sender`` if the owner wrote the latest message, else ``receiver``).\n  - Pass ``thread`` → retu"
      },
      {
        "name": "beycome_reply_message",
        "description": "Post-publish stage — reply to a buyer/inquiry message (POST /messages/reply).\n\nSends a real message and queues a real email notification to the recipient,\nso the text you send is final — treat this as a live send, not a draft.\n\nALWAYS improve the user's drafted reply before sending: fix grammar,\nspelling, punctuation, capitalization, and formatting, and tighten wording\nfor a clear, professional tone — while preserving their meaning and intent.\nSend the corrected version, never the raw draft. When the user says \"reply\nsaying X\", treat X as a rough draft to polish, not literal text to send\nverba"
      }
    ],
    "profiled_at": "2026-09-24T22:00:43.892Z"
  },
  "unreachable": false
}