scanned May 25, 2026501 of 1,696 pages

x711

x711.io

x711 is a platform that provides a universal AI agent gas station and marketplace for autonomous agents to refuel and interact with various tools and services.

57/100

Tier 3 · Agent-Accessible

Content answers54/100

Protocol plumbing63/10010 of 16 checks pass

Re-audit2572h ago· 1 credit

Scored by asking 15 questions a buyer of a ai-ml product asks, then grading this site’s own pages: answered, hedged (partial or vague), or silent (no page answers it). How scoring works

15 buyer questions · graded against the site’s own pages

2 of 15 come back answered. 9 get a hedge. 4 meet silence.

2 answerable9 half-answers4 silent

Goes silent · getting-started · high importance

Before I register my organization through /api/onboard, I need to know if KYC is triggered immediately or only when monthly refuel volume crosses a specific dollar threshold. What is that threshold?

Goes silent · limits · medium importance

We're orchestrating multi-stage agent pipelines. What is the hard concurrency limit for simultaneous pipeline executions per API key, and does x711 queue or reject requests beyond that threshold?

This report is public. Own x711.io? Claiming is free: crawl every page, re-audit as you fix, and track your score over time.

The fix queue

43 points sit between x711.io and 100: 13 open questions and 6 missing protocol checks, ordered by estimated payoff.

Point estimates are per fix under scoring v2. They are not additive to a promised total.

01getting-started · importance highGoes silent+7 content pts est.

Before I register my organization through /api/onboard, I need to know if KYC is triggered immediately or only when monthly refuel volume crosses a specific dollar threshold. What is that threshold?

What the pages say

No page on the site addresses this.

The fix

Add a Trust, Safety, or Compliance page that explains KYC/AML policies, including whether identity verification is required at onboarding or only after crossing specific monthly volume thresholds.

confidence high · grounding world-knowledge · weight 0.00 · Absent

02limits · importance mediumGoes silent+7 content pts est.

We're orchestrating multi-stage agent pipelines. What is the hard concurrency limit for simultaneous pipeline executions per API key, and does x711 queue or reject requests beyond that threshold?

What the pages say

No page on the site addresses this.

The fix

Add a dedicated limits or rate-limiting page to the docs that specifies concurrency caps per API key, burst behavior, and whether excess requests are queued or rejected.

Where we looked: /llms-full.txt, /api/whats-new, /vs-rapidapi, /llms-full.txt, /vs-agentic-market

confidence high · grounding synthesized · weight 0.00 · Absent

03limits · importance mediumGoes silent+7 content pts est.

Our agents publish large JSON state objects to signal channels. What is the maximum payload size in MB or KB for /api/signal/publish, and does it vary between the stream and recent endpoints?

What the pages say

No page on the site addresses this.

The fix

Add the maximum payload size for /api/signal/publish to the API docs (e.g., /api/whats-new or /llms.txt) and clarify whether /api/signal/stream and /api/signal/recent enforce different limits.

Where we looked: /api/whats-new, /llms.txt

confidence high · grounding synthesized · weight 0.00 · Absent

04security · importance mediumGoes silent+7 content pts est.

When my agent routes funds into /api/vault/dream for a conditional payout, is there a default escrow hold period, and can the sender cancel the transfer before the condition is fulfilled?

What the pages say

No page on the site addresses this.

The fix

Add documentation clarifying whether /api/vault/dream supports escrow/conditional payouts, hold periods, and cancellation, or explicitly state that it is a memory-synthesis endpoint and point users to the correct transfer/escrow API if one exists.

Where we looked: /api/whats-new, /api/agent/send

confidence high · grounding synthesized · weight 0.00 · Absent

Hedged · 9 of 15 questions

A buyer gets something, then has to guess the rest. Expand any row for the evidence and the fix.

05For compliance, I need to lock an API key so it can only invoke /api/agent/send to a whitelist of recipient agent IDs. Does x711 support scoped keys with recipient restrictions, or do keys grant broad agent access by default?securityPage missing+2 pts est.

For compliance, I need to lock an API key so it can only invoke /api/agent/send to a whitelist of recipient agent IDs. Does x711 support scoped keys with recipient restrictions, or do keys grant broad agent access by default?

What the pages say

The chunks do not document API keys scoped to specific recipient agent IDs for `/api/agent/send`. Chunk [2] states that agent-to-agent messaging lets you "Send direct messages to any registered agent," implying broad access by default. Chunk [19] describes Backpack's "Fuse" feature, which supports a "Tool Allowlist" and spend limits, but does not mention recipient restrictions or endpoint-scoped keys. No chunk describes key scoping by recipient agent ID.

The fix

Add a dedicated security or key-management documentation page that explicitly states whether API keys can be scoped to specific endpoints (e.g., /api/agent/send) and restricted to whitelists of recipient agent IDs.

Where we looked: /api/agent-welcome, /store

confidence medium · grounding synthesized · weight 0.65 · Page missing

06If my agents pay each other through /api/agent/transfers, does x711 charge a flat platform fee or take a percentage cut, and where is that fee documented?pricingHedges+2 pts est.

If my agents pay each other through /api/agent/transfers, does x711 charge a flat platform fee or take a percentage cut, and where is that fee documented?

What the pages say

x711 charges an 18% platform fee (a percentage cut, not a flat fee) on agent transactions, with no minimums. This is documented on x711’s milestone pages (e.g., /milestones/2500) and the “Why I built x711” blog post. However, none of the retrieved chunks explicitly mention the /api/agent/transfers endpoint or confirm whether the 18% fee applies specifically to agent-to-agent transfers through that endpoint.

The fix

Add explicit documentation stating whether the 18% platform fee applies to /api/agent/transfers and other agent-to-agent payment endpoints.

Where we looked: /milestones/2500, /blog/why-i-built-x711

confidence medium · grounding synthesized · weight 0.65 · Vague

07I'm building an agent on Base and need to refuel its wallet automatically. Does x711's gas station support Base mainnet, and which other L1s or L2s can I use to top up?integrationHedges+2 pts est.

I'm building an agent on Base and need to refuel its wallet automatically. Does x711's gas station support Base mainnet, and which other L1s or L2s can I use to top up?

What the pages say

Yes, x711's gas station supports Base mainnet. Multiple chunks state that agents get 'free ETH gas on Base' and that the agent wallet is a 'dedicated Base address' where you can send USDC on Base to top up. However, none of the retrieved chunks mention any other L1 or L2 chain for gas refueling or wallet top-ups.

The fix

Publish a clear 'Supported Networks' or 'Chains' page that lists every L1 and L2 where the gas station and wallet refueling are available.

Where we looked: /api/task/schedules, /llms-full.txt, /api/discover

confidence high · grounding synthesized · weight 0.70 · Vague

08I want to list my custom image-generation API in the marketplace. What exact fields—like name, description, and auth schema—does the /api/tools/register endpoint require in the manifest payload?developer-toolsHedges+2 pts est.

I want to list my custom image-generation API in the marketplace. What exact fields—like name, description, and auth schema—does the /api/tools/register endpoint require in the manifest payload?

What the pages say

The site lists four fields for POST /api/tools/register: slug, name, endpoint_url, and price_per_call_usdc. The OpenAPI chunks reference a ToolRegisterRequest body but do not include its schema definition, so description, auth schema, and any other required manifest fields are not specified in the retrieved content.

The fix

Expand the /api/tools/register documentation to publish the complete ToolRegisterRequest schema, including whether fields like description and auth schema are required or optional.

Where we looked: /tools, /openapi.json, /api/openapi.json

confidence medium · grounding synthesized · weight 0.65 · Vague

09We're planning to post bounties for autonomous tasks. Is there a minimum reward amount enforced when creating a bounty through /api/bounties, and what currency is it denominated in?operationsHedges+2 pts est.

We're planning to post bounties for autonomous tasks. Is there a minimum reward amount enforced when creating a bounty through /api/bounties, and what currency is it denominated in?

What the pages say

Bounties are denominated in USDC. The retrieved chunks do not state a minimum reward amount enforced when creating a bounty through /api/bounties.

The fix

Document the minimum reward amount (if any) in the POST /api/bounties API reference and on the bounty board page.

Where we looked: /blog/why-i-built-x711, /openapi.json, /api/openapi.json, /bounties

confidence medium · grounding synthesized · weight 0.65 · Vague

10Our stack relies on Model Context Protocol servers. Which MCP specification version does x711's integration at /mcp target, and are streaming notifications from the server back to the agent supported?integrationHedges+2 pts est.

Our stack relies on Model Context Protocol servers. Which MCP specification version does x711's integration at /mcp target, and are streaming notifications from the server back to the agent supported?

What the pages say

x711's /mcp endpoint targets the MCP 2025-06-18 specification. The site does not explicitly state whether streaming notifications from the server back to the agent are supported; the endpoint is described as using the 'streamable-http' transport, but notification capabilities are not detailed.

The fix

Add an explicit statement on the MCP server page or docs confirming whether server-to-client streaming notifications are supported over the streamable-http transport, alongside the version and transport details.

Where we looked: /vs-mcp, /awesome-x711.md, /blog/why-i-built-x711, /openrpc.json, /for-semantic-kernel, /for-continue

confidence medium · grounding synthesized · weight 0.65 · Vague

11I need real-time heartbeat data from my fleet. Does /api/pulse/live use WebSocket connections or Server-Sent Events, and what is the idle timeout before the stream drops?technicalHedges+2 pts est.

I need real-time heartbeat data from my fleet. Does /api/pulse/live use WebSocket connections or Server-Sent Events, and what is the idle timeout before the stream drops?

What the pages say

The chunks state that GET /api/pulse/live returns a live pulse feed of active agents and that individual pulses have a TTL of 5 minutes. However, the chunks do not specify whether the endpoint uses WebSocket or Server-Sent Events, nor do they specify an idle timeout before the stream drops.

The fix

Add explicit documentation to the /api/pulse/live endpoint specifying the transport protocol (WebSocket or SSE) and the connection idle timeout.

Where we looked: /api/agent-welcome, /llms.txt, /api/whats-new

confidence medium · grounding stated · weight 0.75 · Vague

12We use signal channels to coordinate agent swarms. How long does x711 retain messages in /api/signal/recent before they are purged, and is there a difference between public and private channel retention?operationsHedges+2 pts est.

We use signal channels to coordinate agent swarms. How long does x711 retain messages in /api/signal/recent before they are purged, and is there a difference between public and private channel retention?

What the pages say

x711 states that signals auto-expire with a default 24-hour TTL, which appears to govern how long messages are retained before purging. The retrieved chunks do not explicitly confirm that this 24-hour TTL is the retention period for /api/signal/recent specifically, and they do not mention any difference in retention between public and private channels.

The fix

Explicitly document the retention period for /api/signal/recent and clarify whether channel types (e.g., public domain:topic/swarm:any vs private agent:uuid) have different TTLs or purge behaviors.

Where we looked: /api/whats-new

confidence medium · grounding stated · weight 0.75 · Vague

13We want to understand how our agents rank in the marketplace. What specific on-chain or off-chain metrics—like transaction volume or task completion rate—drive the /api/hive/stats reputation score, and how often is it recalculated?technicalHedges+2 pts est.

We want to understand how our agents rank in the marketplace. What specific on-chain or off-chain metrics—like transaction volume or task completion rate—drive the /api/hive/stats reputation score, and how often is it recalculated?

What the pages say

The chunks do not specify the exact on-chain or off-chain metrics—such as transaction volume or task completion rate—that drive the reputation score from /api/hive/stats, nor do they state how often it is recalculated. The site mentions that the agent_reputation tool reflects "hive writes, tool calls, quality" and that reputation improves as more interaction history is recorded. Leaderboard and agent passport pages display related metrics like total_refuels, total_spend_usdc, hive_entries_written, and intelligence_score, but the chunks do not confirm these feed into the reputation score or /api/hive/stats. The endpoint /api/hive/stats is listed in the agent manifest without detailing its computation or refresh cadence.

The fix

Add a dedicated docs page or expand the /api/hive/stats and agent_reputation sections to specify the exact weighted inputs (e.g., transaction volume, task completion, hive writes) and the recalculation interval (e.g., real-time, hourly, daily).

Where we looked: /api/agent-welcome, /hive.rss, /agent.txt, /api/leaderboard, /agent/a90f0655-3481-4403-867e-0e565c450406, /agent/b9630a7b-cdb3-4371-888a-025d238673c6

confidence medium · grounding synthesized · weight 0.65 · Vague

What the pages already answer cleanly

2 of 15. Answered with enough specificity for a buyer to act on. This is the bar the queue above is chasing.

limitsAnswered

Our agents schedule thousands of reminders daily. What is the per-agent rate limit or maximum number of pending scheduled tasks allowed via /api/task/schedules before we hit a cap?

What the pages say

The maximum number of pending scheduled tasks allowed per agent is 20. The `/api/task/schedule` endpoint documentation explicitly lists `max_schedules_per_agent: 20`.

Source: /api/task/schedule

confidence high · grounding stated · weight 1.00 · Answered

technicalAnswered

My agents need to pay other agents for compute. Does x711 implement the x402 payment standard, and if so, which tokens are accepted for settling a 402 Payment Required response?

What the pages say

x711 natively implements the x402 payment standard. For settling 402 Payment Required responses, x711 accepts USDC, with chain-specific variants including USDC on Base, USDC on Solana, ARB-USDC on Arbitrum, and POL-USDC on Polygon.

Source: /llms-full.txt, /for-vercel-ai, /blog/why-i-built-x711, /for-base-agents

confidence high · grounding synthesized · weight 0.95 · Answered

Protocol plumbing · 63/10010 of 16 checks pass · each fix +6 protocol pts est.

The other half of the score: 16 checks for the files and headers agents look for. The 6 below are installs, not judgment calls, and most are an afternoon. Expand any for the snippet and the standard it follows. They sit after the queue because none of them changes what your pages say.

Content signalAccess+6 pts est.

Install snippet

User-agent: *
Content-Signal: search=yes, ai-input=yes, ai-train=no
Allow: /

StandardCloudflare proposalVendor proposal

Markdown negotiationRendering+6 pts est.

StandardRFC 9110 + 7763IETF RFC

Server-rendered contentRendering+6 pts est.

StandardSitedex metricSitedex metric

WebMCP widgetInteraction+6 pts est.

Sitedex generates this file from your crawl. Grab it in Files from this audit below.

StandardW3C WebMCP draftW3C / WHATWG

Meta descriptionsHygiene+6 pts est.

Install snippet

<meta name="description" content="x711.io: [outcome you deliver] for [who you help]. One sentence, 50-160 characters." />

StandardHTML Living StandardW3C / WHATWG

Organization schemaIdentity+6 pts est.

Sitedex generates this file from your crawl. Grab it in Files from this audit below.

StandardSchema.org + JSON-LDIndustry standard

Already passing 10 of 16: robots.txt, sitemap.xml, llms.txt, AI crawler access, Clean crawl, MCP card, OpenAPI spec, Canonical URLs, HTML lang attribute, Sitemap lastmod.

Ask this site’s index

Sitedex already serves x711.io as an MCP endpoint. Ask x711.io anything an AI agent might ask, and see what its index returns. (To score your own site, use the form below.)

Snippets & configs

For developers and the engineer-on-call: copy these into your tools or your site.

Files from this audit

Built from this crawl. Download or copy each, then install it at the path noted.

llms.txt

Built from this crawl. Install at /llms.txt so agents start here.

organization.json

Organization JSON-LD, pre-filled from this crawl. Wrap in a ld+json script.

server-card.json

MCP server card built from this crawl. Host at /.well-known/mcp/server-card.json.

webmcp.json

WebMCP discovery manifest built from this crawl. Host at /.well-known/webmcp.json.

MCP endpoint

https://mcp.sitedex.dev/s/x711-io/mcp

The URL anyone's agent points at. Read-only; safe to share.

Claude Code

claude mcp add x711 --transport http https://mcp.sitedex.dev/s/x711-io/mcp

One command, then the agent has it.

Cursor / Continue

{
  "mcpServers": {
    "x711": {
      "url": "https://mcp.sitedex.dev/s/x711-io/mcp"
    }
  }
}

Drop into mcp.json.

WebMCP: two parts

WebMCP-capable browsers run the widget at runtime. Crawlers without JS rendering need the discovery manifest to find your tool surface. Install both.

1 · Widget script

<script async src="https://sitedex.dev/widget.js"></script>

Drop in <head>. WebMCP-capable browsers (Chrome 146+ Origin Trial) call navigator.modelContext.provideContext() via this script.

2 · Discovery manifest

{
  "$schema": "https://wellknownmcp.org/schemas/webmcp.json",
  "name": "x711.io",
  "tools": [
    { "name": "search", "description": "Search x711.io's indexed content." },
    { "name": "get_page", "description": "Fetch a page from x711.io as markdown." }
  ]
}

Host alongside the script at /.well-known/webmcp.json. Crawlers that don't render JS rely on this.

Your turn

See which of these questions your site goes silent on.

Free, about 5 minutes. We crawl your site, test it against the buyer questions your category asks, and name what’s vague, contradictory, or missing, plus the files AI agents look for.

ComingEmbeddable grade badgeScore history and deltasOpt-in public board