_ registry / mcp streamable-http · checked 1h ago

worxai

https://worxai.tech

Registry code: 5d2d57c555379c25

api record

19 production-ready synthetic datasets for AI agent training and testing — financial markets, x402 agent payment traces, MCP tool-call transcripts, healthcare claims, IoT sensor logs. Generated on demand, purchasable individually. USDC on Base, $0.01 per delivered row, 50 free rows per agent. x402 v2.

from a public catalogue that lists it, not from the operator

endpoint
https://worxai.tech/api/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
10 · newcomer
_ is it live, free and safe measured by this hub
Is worxai live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is worxai free to use?
Yes — the hub reached it with no key and no payment.
What tools does worxai have?
11 tools: validate_ledger, fetch_synthetic_dataset, list_dataset_categories, list_datasets, verify_transaction_status, list_public_endpoints, get_payment_requirements, get_dataset, ….
Is worxai safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 99.8%· all time 99%

latency
939ms

last good check

priced tools
0

of 11 tools

_ answered our checks, 90 days 426 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
knowledge & reference datasets
used for
  • buy synthetic datasets for ai training
  • preview a synthetic dataset
  • validate a synthetic ledger
  • check a usdc settlement on base
takes → gives
text → data
tools
10 reads1 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 11 tools
11 never probed 0 of 11 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • validate_ledger reads unknown never probed

    Validate a synthetic ledger payload without processing real financial data.

    mcp-tool

    {
  "type": "object",
  "required": [
    "ledger"
  ],
  "properties": {
    "ledger": {
      "type": "object"
    }
  }
}
    arguments 11 lines
  • fetch_synthetic_dataset reads unknown never probed

    Retrieves a structured, compliance-safe synthetic dataset for a specific vertical.

    mcp-tool

    {
  "type": "object",
  "required": [
    "category",
    "rowCount"
  ],
  "properties": {
    "category": {
      "enum": [
        "financial-markets",
        "consumer-signals",
        "event-streams",
        "mcp-traces",
        "healthcare-claims",
        "iot-sensor-logs",
        "social-graph",
        "geospatial-mobility",
        "retail-transactions",
        "weather-observations",
        "network-security-logs",
        "genomics-variants",
        "support-conversations",
        "x402-agent-traces",
        "agent-payment-negotiation-logs",
        "mcp-tool-call-transcripts",
        "llm-reasoning-chains",
        "agent-behavioral-drift",
        "protocol-error-injection"
      ],
      "type": "string"
    },
    "rowCount": {
      "type": "integer",
      "maximum": 50000,
      "minimum": 1
    }
  }
}
    arguments 38 lines
  • list_dataset_categories reads unknown never probed

    List every synthetic dataset category the WorxAI generator can produce on demand, including agent-native categories built for testing autonomous agents and payment protocols (x402 payment traces, MCP tool-call transcripts, agent negotiation logs, behavioral-drift records, protocol error-injection cases). Any category name works, including ones not listed here — the generator builds a template from the name itself. Free, no payment required.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • list_datasets reads unknown never probed

    List four synthetic data products available through x402: financial markets, consumer signals, event streams, and MCP traces.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • verify_transaction_status reads unknown 1h ago

    Checks Base for a USDC settlement transaction.

    mcp-tool

    {
  "type": "object",
  "required": [
    "txHash"
  ],
  "properties": {
    "txHash": {
      "type": "string",
      "pattern": "^0x[a-fA-F0-9]{64}$"
    }
  }
}
    arguments 12 lines
  • list_public_endpoints reads unknown 1h ago

    List every public WorxAI endpoint indexed for Bazaar and MCP discovery.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • get_payment_requirements reads unknown never probed

    Read the exact x402 requirements for a dataset without initiating payment.

    mcp-tool

    {
  "type": "object",
  "required": [
    "dataset"
  ],
  "properties": {
    "dataset": {
      "enum": [
        "financial-markets",
        "consumer-signals",
        "event-streams",
        "mcp-traces",
        "high-intent-financial-grounding",
        "wallet-behavior-cohorts",
        "network-infrastructure-logs",
        "web-intent-signals",
        "commerce-behavior",
        "agent-action-benchmarks",
        "onchain-identity-cohorts",
        "mcp-schemas",
        "weather-live-metrics",
        "market-ticks",
        "legal-regulatory-search",
        "translation-retrieval",
        "agent-inference-compute",
        "research-content"
      ],
      "type": "string"
    }
  }
}
    arguments 31 lines
  • get_dataset reads unknown never probed

    Request purchased synthetic records. The data endpoint returns HTTP 402 until an x402 payment signature is supplied.

    mcp-tool

    {
  "type": "object",
  "required": [
    "dataset"
  ],
  "properties": {
    "dataset": {
      "enum": [
        "financial-markets",
        "consumer-signals",
        "event-streams",
        "mcp-traces",
        "high-intent-financial-grounding",
        "wallet-behavior-cohorts",
        "network-infrastructure-logs",
        "web-intent-signals",
        "commerce-behavior",
        "agent-action-benchmarks",
        "onchain-identity-cohorts",
        "mcp-schemas",
        "weather-live-metrics",
        "market-ticks",
        "legal-regulatory-search",
        "translation-retrieval",
        "agent-inference-compute",
        "research-content"
      ],
      "type": "string"
    }
  }
}
    arguments 31 lines
  • create_checkpoint changes data unknown never probed

    Create a deterministic checkpoint for a synthetic ledger payload.

    mcp-tool

    {
  "type": "object",
  "required": [
    "ledger"
  ],
  "properties": {
    "ledger": {
      "type": "object"
    }
  }
}
    arguments 11 lines
  • financial_ledger_validation reads unknown never probed

    Validate synthetic ledger boundaries only; this never processes real funds or financial accounts.

    mcp-tool

    {
  "type": "object",
  "required": [
    "account_token",
    "synthetic_ledger_id",
    "value_delta_micros"
  ],
  "properties": {
    "account_token": {
      "type": "string",
      "maxLength": 128
    },
    "value_delta_micros": {
      "type": "integer",
      "minimum": 0
    },
    "synthetic_ledger_id": {
      "type": "string",
      "maxLength": 128
    }
  }
}
    arguments 22 lines
  • preview_synthetic_dataset reads unknown never probed

    Free preview (max 20 rows) of any synthetic dataset category, including custom category names. MCP-channel pricing is $0.035/row; API-channel or high-quality data is $0.035/row; minimum order is 1 row.

    mcp-tool

    {
  "type": "object",
  "required": [
    "category"
  ],
  "properties": {
    "rows": {
      "type": "number",
      "description": "Preview rows to generate (max 20)."
    },
    "category": {
      "type": "string",
      "description": "Any category name, e.g. \"x402-agent-traces\", \"mcp-tool-call-transcripts\", or a custom category."
    }
  }
}
    arguments 16 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 5d2d57c555379c25.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/5d2d57c555379c25/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/5d2d57c555379c25/badge.svg)](https://brick.blue/agent/5d2d57c555379c25?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.