Platform Capabilities

Listing, promotion, settlement — three things built into one platform

Clients do only what they do best — provide data. The rest: endpoints, being discovered, being cited, collecting payment, revenue sharing, all continuously supplied by Feegate as platform capabilities.

00 · Architecture

What happens during one paid call

01 · Discovery

Agent finds a tool

Get the tool list and price sheet from MCP Registry, llms.txt, or the marketplace catalog.

02 · Challenge

Server returns 402

Contains the four elements network / asset / amount / payTo; the client learns the price without registering.

03 · Signature verification

EIP-3009 authorization

The buyer only needs to hold USDC; gas is sponsored by the facilitator. After signing, replay the request with the credential.

04 · Settlement

settle after successful delivery

No charge when a failure returns isError; on success it goes on-chain, and the platform collects then splits the revenue.

01 · Listing

Turn one dataset into a set of sellable tools

Clients complete the first four steps in the console; the platform handles endpoint generation, settlement integration, and discovery-layer registration.

Four data source integrations

HTTP API (with auth and polling), CSV / file upload, direct PostgreSQL connection, scheduled crawlers. After connecting, you can preview retrieval results directly and confirm data freshness before slicing into tools.

APICSVPostgresCrawler

Tool factory

Slice the data source into the smallest paid units that return within 1 second, then define name, description, input parameters, return fields, and price one by one. The platform checks whether the description is Agent-readable — tools written unclearly will not be bought.

Splitting suggestionsDescription check

Free tier and pricing

At least one free tool (showcase) is required; paid tools default to $0.05. A unit price below $0.01 makes no sense in this system — each facilitator transaction costs about $0.001, so pricing too low means losing money on every sale.

$0.05 defaultRange $0.01–$0.50

Endpoints and settlement: the platform has already done it for you

FastMCP exposes the tools + x402 payment middleware issues the 402 challenge + Base mainnet + Circle USDC + PayAI facilitator. Every link in this chain has pitfalls; we hit them all, so you only need to click Generate endpoint once.

Built in

MCP endpoint + payment middleware

No settlement when a failure returns isError — failed delivery is not charged; that is the foundation of trust.

Built in

Base mainnet + Circle USDC + PayAI

The official x402.org facilitator only supports testnets, and Mogami only has v1 — the cost of choosing wrong is an entire chain that does not work.

Built in

Persistent process · Health checks · Self-healing

Version upgrades and facilitator switchover drills — for teams that do not want to run their own ops.

tools.yaml · Console export
tools:
  - name: ping
    price: "0"          # 免费层
    desc: 健康检查
  - name: list_gpu_models
    price: "0"          # 橱窗
    desc: 全部 GPU 卡型清单
  - name: gpu_price
    price: "0.05"
    params: { gpu: string }
    desc: 指定卡型的当前最低价、中位价与 30 天最低价
  - name: gpu_history
    price: "0.05"
    params: { gpu: string, days: int }
    desc: 30 天价格历史、最低价平台与库存状态
02 · Promotion

Get discovered, get cited, then get bought on the spot

We call it GEO (generative engine optimization). It is not mysticism — it is a five-rung ladder you can work through rung by rung.

Layer 1

Crawlable · Allow in robots, let AI crawlers in

Explicitly allow ClaudeBot, GPTBot, OAI-SearchBot, PerplexityBot, Google-Extended, and add PetalBot, Yeti, Daum, Qwantify and a dozen more sources based on measured logs.Block them, and the next four layers are all for nothing.

Measured: ClaudeBot 15,701 times in 30 days
Layer 2

Understandable · Structured data declaring 'we are the data source'

Write the JSON-LD Dataset node clearly: the downloadable dataset, how many retrieval entry points, update frequency, covered time range, and which fields it contains. Let AI know at the machine level where to fetch data.

Layer 3

Citable · The answer must be 'copy-friendly'

Put a complete answer at the top of the page that can be repeated verbatim: who, how many, when, source URL, license. Large models tend to cite well-formed sentences rather than assemble them from tables themselves.

Layer 4

Learnable · llms.txt + explicit usage instructions

In /llms.txt, state what the site is, how the data is used, how much is free, and how to cite it (How to cite). This file is becoming the de facto standard for AI crawling.

Layer 5

Payable · After being cited, it must be buyable on the spot

The layer most people miss: after AI mentions you, users who want to dig deeper need a path that requires no registration and no waiting for a sales reply.Citations bring attention; settlement turns attention into revenue.

Feegate fills this layer
Distribution

Catalog distribution

Submit to the official MCP Registry (publish the tool as a binary via GitHub releases — the package with the same name on npm is fake), llms.txt directories, and AI-friendly site indexes.

Placement

Marketplace slots and recommendations

Featured slots on the data marketplace homepage, category pinning, on-site cross-recommendations. Clients under the collection model can apply to join joint promotions.

Measurement

Citation tracking

Crawl logs split by crawler source, AI session referral traffic stats, direct-answer card hit counts. You can only fix a layer you can see.

03 · Settlement

Collection, commission, settlement — all follow the on-chain record

The platform collects USDC → aggregated by calendar month, settled on the 10th of the next month → settlement statements are exportable. Reconciliation trusts only Transfer events.

Settlement network
Base mainnet

eip155:8453

Pricing asset
USDC

Official Circle contract

Buyer requirements
No ETH needed

Gas-free sponsored authorization

Payment confirmation
Check Transfer

No balance deltas

When verifying real money flows:Trust only on-chain Transfer events—balance differences get fooled by RPC sync lag. The console's reconciliation panel aggregates by Transfer events by default.

Revenue-sharing rules

Under the collection model, each transaction amount is distributed in this order:

Transaction amount (USDC)$1.00
Platform commission 50%-$0.50
facilitator settlement cost-$0.001
Client payout (settled on the 10th of the next month)$0.499
Minimum settlement amount
$50.00 · Below the threshold, it automatically rolls over to the next cycle
Settlement cycle
Every Monday at 00:00 UTC, generate last week's settlement statement
View settlement history in the console
04 · Data standards

Without a unified standard, price comparison does not hold

The same H100 has a dozen different quoting conventions across a dozen platforms. Without unified fields, Agent cannot make decisions for humans.

FieldRequiredDefinition and constraints
platform_idRequireda lowercase stable identifier.Does not change when the brand is renamed; historical continuity takes priority over readability
gpu_modelRequiredmodel + VRAM, e.g. H100 80GB; no abbreviations, no aliases
unitRequiredfixed to hour, all other units are converted by the consumer and never mixed into the source data
currencyRequiredISO 4217 (CNY / USD), with the exchange rate reference time
billingRequiredon-demand / reserved / spot One of three,Different billing types are not allowed in the same ranking
stockRequiredin-stock / limited / out; Out-of-stock quotes must be explicitly marked
regionRequiredPlatform registration / datacenter region (China / North America / Europe / Asia-Pacific…)
includesOptionalList of items included in the price (CPU / memory / storage / network); missing means 'not declared', not 'all included'
observed_atRequiredISO 8601 fetch timestamp; together with refresh_minutes it expresses freshness
licenseRequiredCitation license, CC BY 4.0 recommended; also specify the attribution format
Hard rule 1:"Stability score" can only mean:This site's monitoring coverage of the platform, not platform service quality—this must be stated on every page that uses that score.
Hard rule 2:Historical series are append-only; any correction is added as a new record, and retroactive changes to old values are not allowed.

First turn the data into something Agent can buy

Then take a share from the increment. Compute platforms can also offset service fees with existing referral programs or per-click settlement.