intel.opusai.work

https://intel.opusai.work/v1/ecosystem
down

Shares a payout wallet with 4 other endpoints — its adoption is attributed from that shared wallet's traffic, not earned exclusively.

Population statistics for the x402 machine-payment market. Bands paid volume by how many distinct wallets paid for each endpoint, separating open demand from volume running between a single buyer and seller. Returns demand concentration, repeat-usage distribution, pricing, metadata quality, category mix with demand per listing, and day-over-day change from our own daily snapshots. No provider is named, rated or endorsed.

49
reliability

Reliability & health

Uptime and response time from our own unpaid probes, plus the reliability score built from them.

Uptime

0.0% avg
0% 50% 100% Wed 3 PMFri 3 PMSun 4 PMTue 5 PM

Response time

0ms 50ms 100ms Wed 3 PMFri 3 PMSun 4 PMTue 5 PM
Data table
Reliability history per time bucket over the last 7 days (hourly).
Bucket Uptime Probes Response time
9/30/2026, 3:00:00 PM 0% 1 —
10/1/2026, 3:00:00 PM 0% 1 —
10/2/2026, 3:00:00 PM 0% 1 —
10/3/2026, 3:00:00 PM 0% 1 —
10/4/2026, 4:00:00 PM 0% 1 —
10/5/2026, 4:00:00 PM 0% 1 —
10/6/2026, 5:00:00 PM 0% 1 —
49
Composite reliability — the weighted average of the dimensions below, on a 0–100 scale.
Availability
73

How often it was reachable when we probed it (weight 35%).

Latency
not yet measured

How quickly it answers when it is up — fast scores high (weight 20%).

Security
100

Whether it serves over working TLS / https (weight 15%).

Transparency
61

Whether the operator disclosed what it does — description, schema, identity (weight 15%).

Activity
2

Observed on-chain payments to this endpoint's wallet — transactions, volume, and distinct paying wallets over the last month (weight 15%; not yet measured when we have not seen its wallet settle).

Confidence 100% — how much probe evidence backs this score. A thin history is flagged, not hidden.

See the scoring methodology for exactly how each number is computed.

Payment

Currencies
USDC
Networks
base
Facilitator
unknown
SDK
unknown

Operator

Company
inferred — unknown
Jurisdiction
—
Registrar
Cloudflare, Inc.
Domain registered
2026-09-17
Hosting network
CLOUDFLARENET
Hosting country
—

Operator context is derived from public RDAP/TLS records and unverified. Company and country are only available for endpoints that publish them (an OV/EV TLS certificate or a non-redacted domain record); most endpoints are CDN-fronted and disclose neither.

On-chain activity (base)

10
payments (30d)
0.25
USD volume (30d)
3
paying wallets (30d)

Payments per day

last payment 9/21/2026
0 4 8 Sep 17Sep 19Sep 21
Data table
Settled payments per day.
Day Payments Volume (USD) Paying wallets
9/17/2026 1 0.02 1
9/19/2026 8 0.18 2
9/21/2026 1 0.05 1

This payout wallet is shared: figures cover all 5 endpoints paid at it, since payments cannot be attributed to one of them. Only payments settled on chains and facilitators we index.

Linked by wallet — likely same operator

On-chain agent identity and the x402 endpoint that shares its settlement wallet.

Response schema
{
  "properties": {
    "category_mix": {
      "description": "Resources, providers, call share, median price and median repeat ratio per inferred category, with a note flagging categories carrying many listings and disproportionately little demand.",
      "type": "object"
    },
    "change": {
      "description": "Difference between the earliest and latest locally stored daily snapshots: listings added and delisted, a normalized daily delist rate, and how many survivors grew or shrank. Reports available=false with an explanation until a second day exists; the upstream API publishes a rolling window only, so this cannot be backfilled.",
      "type": "object"
    },
    "concentration": {
      "description": "Share of total paid calls held by the top 1% and top 10% of resources and providers, and the count needed to reach half of all volume. Reported as a distribution, never as a leaderboard.",
      "type": "object"
    },
    "coverage": {
      "description": "Population size, provider count, how many listings took any paid call in the window, and how many days of local observation the change fields rest on.",
      "type": "object"
    },
    "disclaimer": {
      "type": "string"
    },
    "market_structure": {
      "description": "Paid volume banded by how many distinct wallets paid for each endpoint, with the share running through endpoints of two payers or fewer against the share reaching ten or more. Volume on a one-payer endpoint is a private arrangement, not reachable demand; headline totals for this market do not separate the two.",
      "type": "object"
    },
    "metadata_quality": {
      "description": "How many listings publish an output schema or example, and how many carry a description too short to act on. Where this is low, trying a new endpoint costs a paid call with an unknown payload.",
      "type": "object"
    },
    "method": {
      "type": "object"
    },
    "networks": {
      "items": {
        "type": "object"
      },
      "type": "array"
    },
    "pricing": {
      "description": "Advertised price per call: percentiles and tail shares.",
      "type": "object"
    },
    "provider_breadth": {
      "type": "object"
    },
    "repeat_usage": {
      "description": "Calls per unique payer: p10, median, p90, and the share below 1.5. A ratio near 1 is a single-use pattern and cannot be distinguished from inorganic volume; a ratio in the tens is the one demand signal here that is expensive to fake.",
      "type": "object"
    }
  },
  "required": [
    "coverage",
    "concentration",
    "market_structure",
    "repeat_usage",
    "method"
  ],
  "type": "object"
}