Skip to content
bittensor.market
Menu

Staging · Public test environment

Methodology

How listings get here, what we check, and what we do not claim.

Where the data comes from

  1. The indexer reads service records (SubtensorModule.Services) and subnet identities from the Bittensor chain, read-only, at a single block.
  2. It fetches each record's service document with strict safety rules: HTTPS only, public addresses only, no redirects, size and time limits.
  3. The document is validated. Its endpoints and payment methods are stored as the publisher's claims.
  4. Changes are recorded; records that disappear from the chain are marked retired.
  5. Each sync, every published endpoint gets two light, unpaid checks with the same safety rules: one request to its base URL where only the status line is read (any answer below HTTP 500 counts as "answers"), and, if published, one download of its OpenAPI description, which is validated but never executed. No real API request is made and nothing is paid.

The chain only stores a URL and does not check what the document says. A subnet ID is not a permanent identity of a project.

Status levels

Discovered
A service record exists on chain, but no valid service document was found.
Docs valid
The published service document is valid. Endpoints have not been verified yet.
Endpoint verified
The endpoint answers and its published OpenAPI description is valid. No real request was made, so behaviour and quality are not verified.
Callable tested
An approved real request succeeded.
Payment tested
A payment worked in a controlled test.
Degraded
Repeated errors in recent checks.
Unavailable
Not reachable in recent checks.
Retired
No longer published on chain.

Verification describes technical checks only. It is never a guarantee of availability or of the quality of any AI output.

Verification levels for products

Each level needs its own evidence. They are never mixed or upgraded implicitly.

Documented
Described on the provider's public pages. Nothing has been checked yet.
Endpoint reachable
bittensor.market's unpaid check got an answer from a documented URL.
API verified
The API answers and its published OpenAPI description is valid. No paid request was made.
Execution tested
A real request built from the access manifest returned a real provider answer (our internal test client).
x402 testnet payment verified
A paid x402 request settled on a testnet. Not a mainnet payment.
Mainnet payment verified
A paid request settled on mainnet.
Not tested
No test has been run for this.
Not covered
The access method is not documented precisely enough to call directly.

How the integration-readiness ranking works

The ranking on the home page uses only facts we can show. No usage, traffic or payment volumes are tracked or estimated. Points per service:

  • +3 live execution tested with our internal test client (see the test record)
  • +3 a direct call is fully documented (access manifest: endpoint and a documented access method)
  • +2 at least one operation with fully documented parameters (auto-executable)
  • +1 per supported access method, up to 2
  • +2 API verified (answers and valid OpenAPI spec), or +1 endpoint reachable
  • +1 free (keyless) access · +1 docs published
  • −1 when the researched data is older than 60 days

Ties are ordered by name. Each entry shows its reasons on hover. Search results put text relevance first, then the same facts; with include=access the API returns the score and reasons per result.

What we never do

  • Proxy or relay requests to providers.
  • Hold funds, issue invoices, settle payments or take a cut of provider payments.
  • Ask for or store seed phrases, private keys or wallet secrets.
  • Invent prices, ratings, uptime or usage numbers. Unknown values are shown as unknown.
  • Mix test data into the live catalog.

Independence

bittensor.market is an independent project. It is not affiliated with, endorsed by or operated by the Opentensor Foundation or any subnet listed here. Listing order and ranking follow published, rule-based criteria.