X2Y2
X2Y2 is an NFT marketplace and trading platform on Ethereum offering REST APIs for querying listings, offers, sales history, collection statistics, and executing NFT trades. It provides one of the lowest marketplace fees in the industry at 0.5% and includes an NFT-backed lending (Fi) API suite alongside its core marketplace API.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles X2Y2 the way a machine reads it — 12 machine-readable artifacts across 8 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — X2Y2 scores 32.0/100 (thin), with a separate agent-readiness read of 41/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile X2Y2
Each block below is one kind of artifact we hold for X2Y2. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 8
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
X2Y2 Chain API
The Chain API from X2Y2 — 4 operation(s) for chain.
X2Y2 Contracts API
The Contracts API from X2Y2 — 2 operation(s) for contracts.
X2Y2 Events API
The Events API from X2Y2 — 1 operation(s) for events.
X2Y2 General API
The General API from X2Y2 — 1 operation(s) for general.
X2Y2 Loan API
The Loan API from X2Y2 — 1 operation(s) for loan.
X2Y2 Offer API
The Offer API from X2Y2 — 4 operation(s) for offer.
X2Y2 Offers API
The Offers API from X2Y2 — 1 operation(s) for offers.
X2Y2 Orders API
The Orders API from X2Y2 — 4 operation(s) for orders.
Scroll within the panel for all 8 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Apis Context
JSON-LDSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for X2Y2 — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
← All providers · Data indexed from github.com/api-evangelist/x2y2 · machine-readable index on apis.io