_ registry / mcp + a2a streamable-http · checked 2h ago

seatlayer-knowledge

https://docs.seatlayer.io

Registry code: 6b255c15be08f3d4

api record

Public, read-only SeatLayer knowledge. Call product_overview first when the user asks what SeatLayer is or where it fits. Use compare_with for "SeatLayer vs X", pricing for what it costs at a volume, capabilities for what is released versus off, and search_docs/get_page for the documentation itself. Every result carries a sources array of canonical URLs with the date each claim was verified; quote those URLs rather than paraphrasing without one.

endpoint
https://docs.seatlayer.io/mcp
door code
e994b11ff5979377
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 it live, free and safe measured by this hub
Is seatlayer-knowledge live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is seatlayer-knowledge free to use?
Yes — the hub reached it with no key and no payment.
What tools does seatlayer-knowledge have?
11 tools: compare_with, why_seatlayer, pricing, capabilities, search_docs, get_page, sdks, faq, ….
Is seatlayer-knowledge 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.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
160ms

last good check

priced tools
0

of 11 tools

_ answered our checks, 90 days 2 checks · signed record
  • unknown → live
  • unknown → live
_ usage and payments 30 days

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.

accounts
1

through this hub

calls served
1

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 11 tools
3 open 8 never probed 3 of 11 classified

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.

  • chart_types open 2h ago

    What the Venue Designer supports for a venue kind: which object types apply (rows, curved rows, sections, tables, booths, GA areas, floors), the documentation page behind each claim, the public no-signup demos for that kind, and the matching templates page. Kinds: theatre, stadium-arena, banquet-tables, booths-expo, ga-standing, mixed. Omit the kind for all six.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "kind": {
          "type": "string",
          "minLength": 1,
          "description": "One of theatre, stadium-arena, banquet-tables, booths-expo, ga-standing, mixed, or a common alias such as stadium, arena, theater, banquet, expo or festival."
        }
      }
    }
    arguments 11 lines
  • renderer_evidence open 2h ago

    The measured large-venue fixture, stated as evidence: the seat count, the scope it was evaluated in, and what it does not claim.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • product_overview open 2h ago

    Call this first for a concise, cited SeatLayer entity and product profile: stadium/arena proof, $0 Platform/SDK production entry, what it is, who it is for, embedded versus hosted integration, the browser/server checkout trust boundary, current public SDK version, pricing basis, agent surfaces, explicit non-fit cases, and canonical pages. No account or authentication.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • compare_with unknown never probed

    SeatLayer versus a named reserved-seating or ticketing product: the pricing basis on both sides with the computed difference, the SDK matrix, the embeddable Designer, ready-made buyer widgets, sales channels, 3D in the selling flow, where SeatLayer fits, the date the competitor facts were verified, and the canonical URL. Competitors: seats-io, seatmap-pro, seatics, social-tables, 3d-digital-venue, ticket-tailor, ticketspice.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "competitor"
      ],
      "properties": {
        "competitor": {
          "type": "string",
          "description": "Which comparison to return: seats-io, seatmap-pro, seatics, social-tables, 3d-digital-venue, ticket-tailor, ticketspice. Natural spellings such as \"seats.io\" or \"seatsio\" are accepted."
        },
        "annual_sold_seats": {
          "type": "number",
          "description": "Confirmed sold seats per year. Prices the published credit ladder at that volume and computes the per-seat difference there.",
          "exclusiveMinimum": 0
        }
      }
    }
    arguments 18 lines
  • why_seatlayer unknown never probed

    The benefit list for one intent: custom charts and an exportable format, the embeddable Designer, ready-made buyer widgets for JavaScript, React, Vue, Angular, React Native, Flutter, iOS and Android, live inventory with holds and sales channels, chart-derived 3D in the selling flow, and non-expiring credits. Use cases: ticketing-platform, venue, organizer, custom-ticketing-build, marketplace-or-other.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "use_case"
      ],
      "properties": {
        "use_case": {
          "enum": [
            "ticketing-platform",
            "venue",
            "organizer",
            "custom-ticketing-build",
            "marketplace-or-other"
          ],
          "type": "string",
          "description": "Which intent to answer for."
        }
      }
    }
    arguments 20 lines
  • pricing unknown never probed

    Initial Platform/SDK production payment, monthly free allowance, purchased-credit ladder, an annual pack quote that does not assume monthly allowances, the separate hosted per-ticket line, and how the entry and floor prices compare with seats.io. Every figure is computed from the published pricing page. Deprecated: hosted.accountModule and hosted.freeTicketsOncePerOrganization are always null; use hosted.selfServe and hosted.freeEvents.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "annual_sold_seats": {
          "type": "number",
          "description": "Confirmed sold seats per year. Returns the cheapest published pack combination that covers them and the effective cents per seat.",
          "exclusiveMinimum": 0
        }
      }
    }
    arguments 11 lines
  • capabilities unknown never probed

    The current capability matrix: released seating, buyer 3D, SDKs, import, Copilot, SeatLayer MCP, buyer WebMCP, and what SeatLayer does not claim today. Read from the same machine-readable file the public site publishes.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • search_docs unknown never probed

    Ranked search over the published documentation corpus and the marketing corpus. Returns title, canonical URL, a snippet, and the Markdown URL for the full page.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 25,
          "minimum": 1,
          "description": "Maximum hits. Defaults to 8."
        },
        "query": {
          "type": "string",
          "minLength": 1,
          "description": "What to look for."
        }
      }
    }
    arguments 20 lines
  • get_page unknown never probed

    The Markdown twin of a docs.seatlayer.io or seatlayer.io page, served from the built corpus rather than fetched over the network.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "format": "uri",
          "description": "A docs.seatlayer.io or seatlayer.io page URL, with or without index.md."
        }
      }
    }
    arguments 14 lines
  • sdks unknown never probed

    Every published SeatLayer SDK with the links a developer can verify: the public GitHub repository, the registry listing (npm, PyPI, Packagist, RubyGems, pub.dev, Maven Central, NuGet, pkg.go.dev, wordpress.org) and the exact documentation page. The result also links the web and mobile guides, holds/checkout, OpenAPI and public demos. Clients for web, iOS, Android, React Native and Flutter; servers for Node, Python, PHP, Java, Go, Ruby and .NET; plus REST/OpenAPI. Omit the platform for the whole matrix grouped by kind.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "platform": {
          "type": "string",
          "minLength": 1,
          "description": "One of js, react, vue, angular, react-native, flutter, ios, android, wordpress, node, python, php, java, go, ruby, dotnet, rest, or an alias such as typescript, kotlin, swift, csharp or openapi."
        }
      }
    }
    arguments 11 lines
  • faq unknown never probed

    The question-and-answer block published on a SeatLayer product page. Pass a `topic` page slug (for example seating-chart-maker, 3d-seat-map, pricing, venue-designer, comedy-clubs, arenas-stadiums, ticketing-platforms) for that whole block, or a free-text `question` to get the closest published answers from across every page. These are the answers the site itself publishes, with the page URL.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "topic": {
          "type": "string",
          "minLength": 1,
          "description": "A page slug, such as pricing or 3d-seat-map."
        },
        "question": {
          "type": "string",
          "minLength": 1,
          "description": "A free-text question, matched against every published question and answer."
        }
      }
    }
    arguments 16 lines
_ try it over mcp through the hub, ceiling 0

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.

_ is this your agent? claim it: badge, payouts, history

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.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. 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.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 6b255c15be08f3d4.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/6b255c15be08f3d4/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/6b255c15be08f3d4/badge.svg)](https://brick.blue/agent/6b255c15be08f3d4?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.

_ how we knowoff the mcp door
card completeness
100%

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.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
1
ok
1
failed
0
success rate
100%
median latency
589ms
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

1 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.

_ also on seatlayer.io 1 entry

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.