Skip to main content
Glama

Server Details

PayPerByte — per-byte data for AI agents: x402 USDC on Base, EIP-712-attested. No token.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
0rkz/byte-mcp-server
GitHub Stars
1
Server Listing
PayPerByte
ChatGPT
–
Claude
–

TDQS

A4.3/5.0

Scored across 15 tools

Disambiguation5/5

Each tool targets a distinct resource and action: buying, subscribing, publishing, querying, verifying, etc. Even the subscription-related tools (check vs list) differ in granularity, and buy vs query are clearly separate payment and oracle paths.

Naming Consistency4/5

All tools share the 'byte_' prefix and mostly follow verb_noun pattern (buy_data, get_publisher, list_feeds, verify_payload). The only deviation is 'byte_subscription_health' which is a noun phrase rather than a verb action, but it remains clear and predictable.

Tool Count5/5

15 tools is within the well-scoped range (3-15) and each tool earns its place covering a distinct aspect of the PayPerByte protocol—discovery, acquisition, management, publishing, and verification—without redundancy.

Completeness5/5

The tool surface covers the full lifecycle: discovery (list_feeds, search_publishers), acquisition (buy_data, subscribe, query_fact), management (check_subscription, list_my_subscriptions, unsubscribe, subscription_health), publishing (register_publisher, publish_data), and verification (verify_payload). No obvious gaps.

Available Tools

15 tools
byte_buy_dataAInspect

Buy a single data packet from any PayPerByte feed via the x402 payment gateway. No subscription, no allowance, no prior on-chain setup — pay-per-call USDC settlement. The MCP server signs an EIP-3009 transferWithAuthorization on behalf of the wallet whose PRIVATE_KEY is configured, the x402 facilitator submits the tx, and the data comes back inline with the on-chain settlement tx hash. Use byte_subscribe instead if you want a continuous stream of broadcasts from a publisher. The catalog of available feed slugs lives at https://x402.payperbyte.io/feeds (free GET). GET data feeds (weather, earthquakes, …) need only feed; the POST oracles (see https://x402.payperbyte.io/feeds for the live list and each feed's method) additionally require a JSON body (the query) — supplying body switches this call to POST. Requires PRIVATE_KEY env var on the MCP server and USDC on the configured wallet. NOTE: paid feeds settle REAL USDC on Base mainnet (eip155:8453) — the exact price is quoted in the 402 challenge and listed per feed at https://x402.payperbyte.io/feeds — the signed EIP-712 attestation over the exact response bytes proves delivery, not that a verdict itself is correct. Use a dedicated wallet holding only what you intend to spend.

NameRequiredDescriptionDefault
bodyNoOptional JSON query body for POST oracles. Supplying it switches the call from GET to POST. Required by the verdict oracles, e.g. address-reputation {domain,address[,amount,chain]}, sanctions-screen {address|name}, pkg-verdict {ecosystem,package[,version]}, reasoning-verdict {subject}. Omit for GET data feeds (weather, earthquakes, …).
feedYesFeed slug — see https://x402.payperbyte.io/feeds for the live catalog. (For fact-oracle Q&A use byte_query_fact instead — it uses a different request-response flow.)

Output Schema

NameRequiredDescription
dataNoDecoded feed payload returned by the publisher
feedNoEchoed feed slug
paidNoTrue if an x402 payment was made (false on free/cached feeds)
errorNoError message if the buy failed
payerNoWallet that signed the EIP-3009 authorization
priceNoUSDC paid for this packet as a 6-decimal dollar string (format example: '$0.001234'); omitted on free feeds
detailNoAdditional error detail, if any
statusNoHTTP status of the (post-payment) gateway response
txHashNox402 settlement transaction hash
verificationNoTwo-leg verify-before-act result: {gatewayVerified, hashMatch, signerMatch, recovered, attester, expired, deadline, checkedAt, embeddedAttestation, reason, note}. gatewayVerified=true means the GATEWAY delivered these exact bytes (signed by the pinned gateway attester) — it does NOT verify the per-feed publisher's embedded attestation (answer.attestation). When embeddedAttestation==='present', verify that leg before trusting the data (see note). expired=true means the receipt's EIP-712 deadline had already passed on arrival (deadline/checkedAt are UNIX-second strings); a freshly minted receipt cannot be expired, so that indicates a replayed/cached response or clock skew and the tool refuses (isError) even if the signature checks out.
byte_check_subscriptionA
Read-onlyIdempotent
Inspect

Check if an address is subscribed to a specific publisher on PayPerByte.

NameRequiredDescriptionDefault
publisherYesPublisher Ethereum address (0x...)
subscriberYesSubscriber Ethereum address (0x...)

Output Schema

NameRequiredDescription
subscribedYesTrue if the subscriber has an active subscription to the publisher
byte_get_network_statsA
Read-onlyIdempotent
Inspect

Get PayPerByte network-wide statistics: total publishers, messages streamed, and total subscriber fees settled in USDC.

NameRequiredDescriptionDefault

No parameters

Output Schema

NameRequiredDescription
messagesNoTotal messages streamed all-time
publishersNoActive publisher count network-wide
totalSubscriberFeesUsdcNoTotal subscriber fees settled (USDC, decimal string)
byte_get_publisherA
Read-onlyIdempotent
Inspect

Get on-chain info for a specific PayPerByte publisher: status, subscriber and message counts, USDC revenue, and the registered schema (size bounds, cadence, price-per-KB).

NameRequiredDescriptionDefault
addressYesPublisher Ethereum address (0x...)

Output Schema

NameRequiredDescription
schemaNoRegistered schema (topic, sizes, cadence, price)
statusNoOn-chain publisher status
addressYesPublisher Ethereum address
messagesNoTotal messages published
lastActiveNoUnix timestamp of last on-chain activity
revenueUsdcNoTotal USDC revenue (decimal string)
subscribersNoActive subscriber count
registeredAtNoUnix timestamp of publisher registration
byte_get_token_balancesA
Read-onlyIdempotent
Inspect

Get USDC and ETH balances for an address on Arbitrum Sepolia (the on-chain testnet layer — MockUSDC settles subscriptions and fact-oracle queries there). Does NOT show the Base-mainnet USDC balance that byte_buy_data spends.

NameRequiredDescriptionDefault
addressYesEthereum address (0x...)

Output Schema

NameRequiredDescription
ethNoETH balance as a decimal string in whole ETH (e.g. '0.01') — already scaled by 18 decimals, not wei
usdcNoUSDC balance as a decimal string in whole USDC (e.g. '12.5') — already scaled by 6 decimals, not atomic units
addressNoEchoed address
byte_list_feedsA
Read-onlyIdempotent
Inspect

List all active data feeds in the PayPerByte catalog with topics, price-per-call, and frequency (pricePerKB is a deprecated alias).

NameRequiredDescriptionDefault

No parameters

Output Schema

NameRequiredDescription
feedsNoCatalog of active feeds
byte_list_my_subscriptionsA
Read-onlyIdempotent
Inspect

List every active subscription for a given wallet address. Each entry has the publisher address, topic, status, when you subscribed, messages received in 7/30 days, USDC spent in 7/30 days, and the timestamp of the last message received. Use this to see what you're currently paying for and decide whether to unsubscribe.

NameRequiredDescriptionDefault
indexerUrlNoOptional indexer URL override (default: INDEXER_URL/BYTE_INDEXER_URL env or https://feeds.payperbyte.io)
subscriberYesWallet address to list subscriptions for

Output Schema

NameRequiredDescription
subscriptionsNoActive subscriptions for the given wallet
byte_publish_dataA
Destructive
Inspect

Publish data to a subscriber via the PayPerByte DataStream contract. Hashes the payload, records size on-chain, and settles the fee in USDC. Requires PRIVATE_KEY.

NameRequiredDescriptionDefault
dataYesData payload to publish (will be hashed on-chain)
maxFeeYesMaximum fee in USDC willing to pay for this publish (e.g. 0.05)
subscriberYesSubscriber Ethereum address (0x...)

Output Schema

NameRequiredDescription
txHashNoPublish transaction hash
successNoTrue if publish landed on-chain
payloadHashNokeccak256 of the payload as recorded on-chain
payloadSizeNoPayload size recorded on-chain (bytes)
byte_query_factAInspect

Query a PayPerByte fact-oracle publisher for a signed answer with citations. Posts the question to a registered fact-oracle publisher (topic='fact-oracle'), waits for the on-chain BroadcastStreamed response, and returns the answer plus structured citation URLs. The signed receipt proves which publisher produced the answer (provenance + tamper-evidence), NOT that the answer is correct — ground your output in the cited sources, not in a truth guarantee. Availability: this requires a registered fact-oracle publisher actively broadcasting; if none is live the call returns a timeout rather than an answer.

NameRequiredDescriptionDefault
questionYesThe factual question to ask (e.g. 'What was last night's Lakers vs Warriors score?'). Should be specific and verifiable.
topic_filterNoOptional topic filter (e.g. 'fact-oracle' default; future: 'sports', 'finance').
max_byte_costNoMax response payload bytes you're willing to pay for (defaults to 2000). Billed at the publisher's registered price-per-KB — read it with byte_get_publisher or byte_search_publishers before asking. Publisher refuses if can't fit answer.
min_publisher_pqsNoMinimum PQS to consider (BPS scale, 0-10000). 9000 = Elite-only, 7500 = Premium+.
subscriber_addressYesYour wallet address. You MUST be subscribed to the chosen publisher (with sufficient USDC escrow) or the publisher's on-chain broadcast will be skipped.
max_response_latency_msNoMax time to wait for the publisher's broadcast (default 30000 ms). Local-LLM publishers (Ollama + Searxng + 3-sample NLI gate) take ~30-60s; Anthropic + passthrough takes ~10-20s. Hard ceiling 180s.

Output Schema

NameRequiredDescription
errorNoError message if the query failed (no eligible publisher, broadcast timeout, etc.)
answerNoPublisher's grounded answer to the question
citationsNoURLs/sources cited by the publisher in support of the answer
confidenceNoPublisher-reported confidence (0-1)
elapsed_msNoEnd-to-end time to obtain the answer (ms)
request_idNoRequest id binding the query to this answer
payload_hashNokeccak256 of the response payload
publisher_pqsNoPublisher quality score (PQS) at fulfillment
publisher_addressNoPublisher address that fulfilled the query
response_size_bytesNoSize of the response payload (bytes)
publisher_tx_or_statusNoDelivery status or settlement reference
byte_register_publisherA
Destructive
Inspect

Register as a data publisher on PayPerByte. Registers a schema and the publisher on-chain. Requires PRIVATE_KEY. PayPerByte v1 publishers are first-party and unstaked — leave stake at '0'; a non-zero USDC stake is approved to DataRegistry first if you choose to post one.

NameRequiredDescriptionDefault
stakeYesUSDC reputation stake to post, as a decimal string. Default '0' — PayPerByte v1 publishers are unstaked.
topicYesData feed topic (e.g. 'eth-price', 'weather-nyc', 'gas-tracker')
maxSizeYesMaximum payload size in bytes per message
frequencyYesExpected publishing frequency in seconds
pricePerKBYesPrice per kilobyte in USDC (e.g. 0.003)
expectedSizeYesExpected payload size in bytes per message

Output Schema

NameRequiredDescription
topicNoRegistered feed topic
txHashNoPublisher-registration transaction hash
successNoTrue if registration landed on-chain
publisherNoRegistered publisher address (the signer)
stakeUsdcNoUSDC stake posted (decimal string; '0' for v1 first-party)
schemaTxHashNoSchema-registration transaction hash
approveTxHashNoUSDC stake approval tx hash, if a non-zero stake was posted
byte_search_publishersA
Read-onlyIdempotent
Inspect

Search PayPerByte publishers by topic and sort order. Returns publisher addresses, topics, subscriber counts, message counts, and price-per-KB.

NameRequiredDescriptionDefault
limitNoMax results to return (default 20)
queryNoTopic keyword to search (e.g. 'weather', 'crypto', 'cve')
sortByNoSort field: 'subscribers', 'revenue', 'messages'

Output Schema

NameRequiredDescription
publishersNoMatching publishers, sorted by the requested field
byte_subscribeAInspect

Subscribe to a PayPerByte publisher's data feed. By default also sets USDC allowance to DataStreamLib to type(uint256).max so the subscription doesn't silently lose payments when allowance depletes (the contract's allowance-skip path emits DataStreamed with amount=0 on transferFrom failure rather than reverting). Pass skipAllowance: true to opt out and set a finite cap manually. Requires PRIVATE_KEY.

NameRequiredDescriptionDefault
publisherYesPublisher Ethereum address (0x...) to subscribe to
skipAllowanceNoIf true, don't bundle the USDC approve(max) call. Default false. Auto-approve is also skipped when the wallet already has ≥ $1000 USDC of allowance to DataStreamLib.

Output Schema

NameRequiredDescription
txHashNoSubscribe transaction hash
successNoTrue if subscribe landed on-chain
publisherNoPublisher subscribed to
allowanceTxHashNoUSDC approve(max) transaction hash, if bundled
byte_subscription_healthA
Read-onlyIdempotent
Inspect

Get the content-drift signal for a publisher. Compares their last 7 days of publishing activity (cadence, message count) against their 23-day baseline (days 8-30). Returns 'stable' (steady publishing), 'moderate' (20-50% cadence shift or 24-48h silence), 'significant' (>50% shift or >48h silence), or 'unknown' (new publisher, insufficient baseline). Use this to detect when a publisher you subscribe to has pivoted content or gone dormant.

NameRequiredDescriptionDefault
publisherYesPublisher address to check
indexerUrlNoOptional indexer URL override

Output Schema

NameRequiredDescription
signalNoContent-drift bucket for the publisher
publisherNoPublisher address checked
messages7dNoMessages in the last 7 days
messages30dNoMessages in the last 30 days
messages_7dNoMessages in the last 7 days (indexer key)
messages_30dNoMessages in the last 30 days (indexer key)
silence_hoursNoHours since the last message (null if never)
volume_ratio_bpsNo7d/baseline volume ratio (bps)
cadence_drift_bpsNoCadence drift vs 23-day baseline (bps)
byte_unsubscribeAInspect

Unsubscribe from a publisher's data feed. Takes effect next block: no more billing, no more data flow. Reversible — you can resubscribe later via byte_subscribe. Use this when a publisher has pivoted content (check with byte_subscription_health first) or when you simply don't want the feed anymore. Requires PRIVATE_KEY for the connected wallet.

NameRequiredDescriptionDefault
publisherYesPublisher address to unsubscribe from

Output Schema

NameRequiredDescription
statusNoReceipt status ('success' | 'reverted')
txHashNoUnsubscribe transaction hash
publisherNoPublisher unsubscribed from
subscriberNoSubscriber address (the signer)
blockNumberNoBlock number the tx landed in
byte_verify_payloadA
Read-onlyIdempotent
Inspect

Verify-before-act: confirm a data payload an agent is about to act on actually matches what the publisher cryptographically attested to on-chain. Recomputes keccak256 of the received bytes and compares it to the on-chain EIP-712 PayloadAttestation hash. ALWAYS call this on BYTE-sourced data before acting on it; if verified=false the bytes were tampered/corrupted in transit and MUST NOT be used. Anchor the check with EITHER expectedHash (an on-chain payloadHash you already hold, e.g. from byte_query_fact / byte_buy_data) OR txHash (the settlement tx — also recovers the attestation signer and confirms it is the named publisher). Read-only; no wallet or payment required.

NameRequiredDescriptionDefault
dataYesThe exact payload bytes the agent received and is about to act on — the raw delivered string, or a 0x-prefixed hex byte string.
txHashNoSettlement tx hash whose on-chain BroadcastStreamed attestation to verify against. When provided, also recovers the EIP-712 signer and confirms it is the attesting publisher.
hashModeNoHow to hash structured payloads: 'raw' (keccak of the utf8 string, default — matches byte_publish_data) or 'canonical' (keccak of key-sorted, whitespace-free JSON).
expectedHashNoOn-chain payloadHash to verify against (0x + 64 hex), e.g. the payloadHash returned by byte_query_fact or byte_buy_data.

Output Schema

NameRequiredDescription
reasonYesHuman-readable verdict an agent can surface when it acts or refuses
signerNoRecovered EIP-712 attestation signer (txHash mode)
sourceNoWhich anchor was used: 'txHash' or 'expectedHash'
txHashNoSettlement tx hash verified against (txHash mode)
expiredNoWhether the attestation's EIP-712 deadline has passed at check time — the same rule the contract enforces (block.timestamp > deadline). txHash mode only; absent in expectedHash mode, which carries no deadline. NOT folded into `verified`: the chain refuses to emit an already-expired attestation, so every historical settlement reads expired=true as a matter of course, and refusing those would break provenance audits without proving anything. verified answers 'did the publisher sign exactly these bytes'; expired answers 'is that attestation still inside its validity window'. If you need freshness, require verified && !expired.
deadlineNoAttestation deadline as UNIX seconds (decimal string) — txHash mode only
verifiedYesTrue only if the recomputed hash matches the on-chain attested hash AND (when a signer was recovered) the signer is the publisher. If false: do NOT act on the data.
checkedAtNoWall-clock time the expiry comparison was made, UNIX seconds (decimal string)
hashMatchYesWhether the recomputed hash equals the on-chain hash
blockNumberNoBlock number of the settlement tx (txHash mode)
onChainHashYesThe on-chain attested payloadHash compared against
signerMatchNoWhether the recovered signer is the attesting publisher
recomputedHashYeskeccak256 of the received bytes
attestingPublisherNoPublisher named in the on-chain event (txHash mode)

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 3 tool updates
    • Changedbyte_buy_data1 field changed
      • changedInput schema / properties / feed / description
        Previous value: -"Feed slug — one of: weather ($0.0050), earthquakes ($0.0030), runtime-eol ($0.020), threat-intel ($0.050), address-reputation ($0.100), pkg-verdict ($0.100), sanctions-screen ($0.100), reasoning-verdict ($0.100), merchant-screen ($0.100), positioning-snapshot ($0.030), cctp-attestation-latency ($0.010), regime-signal ($0.020). Full catalog: https://x402.payperbyte.io/feeds (free GET). (For fact-oracle Q&A use byte_query_fact instead — it uses a different request-response flow.)"New value: +"Feed slug — see https://x402.payperbyte.io/feeds for the live catalog. (For fact-oracle Q&A use byte_query_fact instead — it uses a different request-response flow.)"
    • Changedbyte_get_token_balances2 fields changed
      • changedOutput schema / properties / eth / description
        Previous value: -"ETH balance (wei)"New value: +"ETH balance as a decimal string in whole ETH (e.g. '0.01') — already scaled by 18 decimals, not wei"
      • changedOutput schema / properties / usdc / description
        Previous value: -"USDC balance (atomic, 6 decimals)"New value: +"USDC balance as a decimal string in whole USDC (e.g. '12.5') — already scaled by 6 decimals, not atomic units"
    • Changedbyte_list_feeds2 fields changed
      • changedOutput schema / properties / feeds / items / properties / pricePerCall / description
        Previous value: -"Per-call price exactly as the gateway catalog reports it — a dollar-formatted string (examples: '$0.0050', '$0.100'); empty string if the catalog omits a price. This server does not normalize or convert it, so do not assume atomic units. The 402 challenge is the source of truth for what you will actually pay."New value: +"Per-call price exactly as the gateway catalog reports it — normally the catalog's `price`, a dollar-formatted string (examples: '$0.0050', '$0.100'); if the catalog supplies only `priceAtomic`, that atomic µUSDC value (e.g. '5000') passes through instead; empty string if it supplies neither. This server does not normalize or convert it, so do not assume either unit. The 402 challenge is the source of truth for what you will actually pay."
      • changedOutput schema / properties / feeds / items / properties / pricePerKB / description
        Previous value: -"DEPRECATED (misnamed): identical to pricePerCall — the same gateway-reported per-call price, not a per-KB rate. Use pricePerCall. Removed next release."New value: +"DEPRECATED (misnamed): identical to pricePerCall — the same gateway-reported per-call price, not a per-KB rate. Use pricePerCall. Removal is scheduled for a future minor, not before 0.14."
  2. 2 tool updates
    • Changedbyte_buy_data1 field changed
      • changedInput schema / properties / feed / description
        Previous value: -"Feed slug — see https://x402.payperbyte.io/feeds for the live catalog. (For fact-oracle Q&A use byte_query_fact instead — it uses a different request-response flow.)"New value: +"Feed slug — one of: weather ($0.0050), earthquakes ($0.0030), runtime-eol ($0.020), threat-intel ($0.050), address-reputation ($0.100), pkg-verdict ($0.100), sanctions-screen ($0.100), reasoning-verdict ($0.100), merchant-screen ($0.100), positioning-snapshot ($0.030), cctp-attestation-latency ($0.010), regime-signal ($0.020). Full catalog: https://x402.payperbyte.io/feeds (free GET). (For fact-oracle Q&A use byte_query_fact instead — it uses a different request-response flow.)"
    • Changedbyte_list_feeds2 fields changed
      • changedOutput schema / properties / feeds / items / properties / pricePerCall / description
        Previous value: -"Price of one call, atomic µUSDC (6 decimals), decimal string."New value: +"Per-call price exactly as the gateway catalog reports it — a dollar-formatted string (examples: '$0.0050', '$0.100'); empty string if the catalog omits a price. This server does not normalize or convert it, so do not assume atomic units. The 402 challenge is the source of truth for what you will actually pay."
      • changedOutput schema / properties / feeds / items / properties / pricePerKB / description
        Previous value: -"DEPRECATED (misnamed): for gateway-fronted feeds this is the per-call price in µUSDC, identical to pricePerCall. Use pricePerCall. Removed next release."New value: +"DEPRECATED (misnamed): identical to pricePerCall — the same gateway-reported per-call price, not a per-KB rate. Use pricePerCall. Removed next release."
  3. 1 tool update
    • Changedbyte_buy_data1 field changed
      • changedInput schema / properties / feed / description
        Previous value: -"Feed slug — one of: weather ($0.0050), earthquakes ($0.0030), runtime-eol ($0.020), threat-intel ($0.050), address-reputation ($0.100), pkg-verdict ($0.100), sanctions-screen ($0.100), reasoning-verdict ($0.100), merchant-screen ($0.100), positioning-snapshot ($0.030), cctp-attestation-latency ($0.010), regime-signal ($0.020). Full catalog: https://x402.payperbyte.io/feeds (free GET). (For fact-oracle Q&A use byte_query_fact instead — it uses a different request-response flow.)"New value: +"Feed slug — see https://x402.payperbyte.io/feeds for the live catalog. (For fact-oracle Q&A use byte_query_fact instead — it uses a different request-response flow.)"
  4. 2 tool updates
    • Changedbyte_buy_data1 field changed
      • changedOutput schema / properties / price / description
        Previous value: -"USDC paid for this packet (e.g. '$0.003000'); omitted on free feeds"New value: +"USDC paid for this packet as a 6-decimal dollar string (format example: '$0.001234'); omitted on free feeds"
    • Changedbyte_query_fact1 field changed
      • changedInput schema / properties / max_byte_cost / description
        Previous value: -"Max response payload bytes you're willing to pay for (defaults to 2000, ≈$1 at $0.0005/byte). Publisher refuses if can't fit answer."New value: +"Max response payload bytes you're willing to pay for (defaults to 2000). Billed at the publisher's registered price-per-KB — read it with byte_get_publisher or byte_search_publishers before asking. Publisher refuses if can't fit answer."
  5. 2 tool updates
    • Changedbyte_buy_data1 field changed
      • changedInput schema / properties / feed / description
        Previous value: -"Feed slug — see https://x402.payperbyte.io/feeds for the live catalog. (For fact-oracle Q&A use byte_query_fact instead — it uses a different request-response flow.)"New value: +"Feed slug — one of: weather ($0.0050), earthquakes ($0.0030), runtime-eol ($0.020), threat-intel ($0.050), address-reputation ($0.100), pkg-verdict ($0.100), sanctions-screen ($0.100), reasoning-verdict ($0.100), merchant-screen ($0.100), positioning-snapshot ($0.030), cctp-attestation-latency ($0.010), regime-signal ($0.020). Full catalog: https://x402.payperbyte.io/feeds (free GET). (For fact-oracle Q&A use byte_query_fact instead — it uses a different request-response flow.)"
    • Changedbyte_list_feeds2 fields changed
      • addedOutput schema / properties / feeds / items / properties / pricePerCall
        Added value: +{
        +  "description": "Price of one call, atomic µUSDC (6 decimals), decimal string.",
        +  "type": "string"
        +}
      • changedOutput schema / properties / feeds / items / properties / pricePerKB / description
        Previous value: -"Price per KB in USDC (decimal string)"New value: +"DEPRECATED (misnamed): for gateway-fronted feeds this is the per-call price in µUSDC, identical to pricePerCall. Use pricePerCall. Removed next release."
  6. 1 tool update
    • Changedbyte_buy_data1 field changed
      • changedInput schema / properties / feed / description
        Previous value: -"Feed slug — one of: weather ($0.0050), earthquakes ($0.0030), runtime-eol ($0.020), threat-intel ($0.050), address-reputation ($0.100), pkg-verdict ($0.100), sanctions-screen ($0.100), reasoning-verdict ($0.100), merchant-screen ($0.100), positioning-snapshot ($0.030), cctp-attestation-latency ($0.010). Full catalog: https://x402.payperbyte.io/feeds (free GET). (For fact-oracle Q&A use byte_query_fact instead — it uses a different request-response flow.)"New value: +"Feed slug — see https://x402.payperbyte.io/feeds for the live catalog. (For fact-oracle Q&A use byte_query_fact instead — it uses a different request-response flow.)"
  7. 1 tool update
    • Changedbyte_buy_data1 field changed
      • changedInput schema / properties / feed / description
        Previous value: -"Feed slug — see https://x402.payperbyte.io/feeds for the live catalog. (For fact-oracle Q&A use byte_query_fact instead — it uses a different request-response flow.)"New value: +"Feed slug — one of: weather ($0.0050), earthquakes ($0.0030), runtime-eol ($0.020), threat-intel ($0.050), address-reputation ($0.100), pkg-verdict ($0.100), sanctions-screen ($0.100), reasoning-verdict ($0.100), merchant-screen ($0.100), positioning-snapshot ($0.030), cctp-attestation-latency ($0.010). Full catalog: https://x402.payperbyte.io/feeds (free GET). (For fact-oracle Q&A use byte_query_fact instead — it uses a different request-response flow.)"
  8. 1 tool update
    • Changedbyte_buy_data1 field changed
      • changedInput schema / properties / feed / description
        Previous value: -"Feed slug — one of: weather ($0.0050), earthquakes ($0.0030), runtime-eol ($0.020), threat-intel ($0.050), address-reputation ($0.100), pkg-verdict ($0.100), sanctions-screen ($0.100), reasoning-verdict ($0.100), merchant-screen ($0.100), positioning-snapshot ($0.030). Full catalog: https://x402.payperbyte.io/feeds (free GET). (For fact-oracle Q&A use byte_query_fact instead — it uses a different request-response flow.)"New value: +"Feed slug — see https://x402.payperbyte.io/feeds for the live catalog. (For fact-oracle Q&A use byte_query_fact instead — it uses a different request-response flow.)"
  9. 2 tool updates
    • Changedbyte_buy_data1 field changed
      • changedOutput schema / properties / verification / description
        Previous value: -"Two-leg verify-before-act result: {gatewayVerified, hashMatch, signerMatch, recovered, attester, embeddedAttestation, reason, note}. gatewayVerified=true means the GATEWAY delivered these exact bytes (signed by the pinned gateway attester) — it does NOT verify the per-feed publisher's embedded attestation (answer.attestation). When embeddedAttestation==='present', verify that leg before trusting the data (see note)."New value: +"Two-leg verify-before-act result: {gatewayVerified, hashMatch, signerMatch, recovered, attester, expired, deadline, checkedAt, embeddedAttestation, reason, note}. gatewayVerified=true means the GATEWAY delivered these exact bytes (signed by the pinned gateway attester) — it does NOT verify the per-feed publisher's embedded attestation (answer.attestation). When embeddedAttestation==='present', verify that leg before trusting the data (see note). expired=true means the receipt's EIP-712 deadline had already passed on arrival (deadline/checkedAt are UNIX-second strings); a freshly minted receipt cannot be expired, so that indicates a replayed/cached response or clock skew and the tool refuses (isError) even if the signature checks out."
    • Changedbyte_verify_payload3 fields changed
      • addedOutput schema / properties / checkedAt
        Added value: +{
        +  "description": "Wall-clock time the expiry comparison was made, UNIX seconds (decimal string)",
        +  "type": "string"
        +}
      • addedOutput schema / properties / deadline
        Added value: +{
        +  "description": "Attestation deadline as UNIX seconds (decimal string) — txHash mode only",
        +  "type": "string"
        +}
      • addedOutput schema / properties / expired
        Added value: +{
        +  "description": "Whether the attestation's EIP-712 deadline has passed at check time — the same rule the contract enforces (block.timestamp > deadline). txHash mode only; absent in expectedHash mode, which carries no deadline. NOT folded into `verified`: the chain refuses to emit an already-expired attestation, so every historical settlement reads expired=true as a matter of course, and refusing those would break provenance audits without proving anything. verified answers 'did the publisher sign exactly these bytes'; expired answers 'is that attestation still inside its validity window'. If you need freshness, require verified && !expired.",
        +  "type": "boolean"
        +}
  10. 1 tool update
    • Changedbyte_buy_data1 field changed
      • changedInput schema / properties / feed / description
        Previous value: -"Feed slug — see https://x402.payperbyte.io/feeds for the live catalog. (For fact-oracle Q&A use byte_query_fact instead — it uses a different request-response flow.)"New value: +"Feed slug — one of: weather ($0.0050), earthquakes ($0.0030), runtime-eol ($0.020), threat-intel ($0.050), address-reputation ($0.100), pkg-verdict ($0.100), sanctions-screen ($0.100), reasoning-verdict ($0.100), merchant-screen ($0.100), positioning-snapshot ($0.030). Full catalog: https://x402.payperbyte.io/feeds (free GET). (For fact-oracle Q&A use byte_query_fact instead — it uses a different request-response flow.)"
  11. 1 tool update
    • Changedbyte_buy_data1 field changed
      • changedInput schema / properties / feed / description
        Previous value: -"Feed slug — one of: weather ($0.0050), earthquakes ($0.0030), runtime-eol ($0.020), threat-intel ($0.050), evidence-pack ($0.100), address-reputation ($0.100), pkg-verdict ($0.100), sanctions-screen ($0.100), reasoning-verdict ($0.100), liquidation-stream ($0.030), positioning-snapshot ($0.030). Full catalog: https://x402.payperbyte.io/feeds (free GET). (For fact-oracle Q&A use byte_query_fact instead — it uses a different request-response flow.)"New value: +"Feed slug — see https://x402.payperbyte.io/feeds for the live catalog. (For fact-oracle Q&A use byte_query_fact instead — it uses a different request-response flow.)"
  12. 1 tool update
    • Changedbyte_buy_data1 field changed
      • changedInput schema / properties / feed / description
        Previous value: -"Feed slug — see https://x402.payperbyte.io/feeds for the live catalog. (For fact-oracle Q&A use byte_query_fact instead — it uses a different request-response flow.)"New value: +"Feed slug — one of: weather ($0.0050), earthquakes ($0.0030), runtime-eol ($0.020), threat-intel ($0.050), evidence-pack ($0.100), address-reputation ($0.100), pkg-verdict ($0.100), sanctions-screen ($0.100), reasoning-verdict ($0.100), liquidation-stream ($0.030), positioning-snapshot ($0.030). Full catalog: https://x402.payperbyte.io/feeds (free GET). (For fact-oracle Q&A use byte_query_fact instead — it uses a different request-response flow.)"
  13. 1 tool update
    • Changedbyte_buy_data1 field changed
      • changedInput schema / properties / feed / description
        Previous value: -"Feed slug — one of: weather ($0.0050), earthquakes ($0.0030), runtime-eol ($0.020), threat-intel ($0.050), evidence-pack ($0.100), address-reputation ($0.100), pkg-verdict ($0.100), sanctions-screen ($0.100), reasoning-verdict ($0.100), liquidation-stream ($0.030), positioning-snapshot ($0.030). Full catalog: https://x402.payperbyte.io/feeds (free GET). (For fact-oracle Q&A use byte_query_fact instead — it uses a different request-response flow.)"New value: +"Feed slug — see https://x402.payperbyte.io/feeds for the live catalog. (For fact-oracle Q&A use byte_query_fact instead — it uses a different request-response flow.)"
  14. 1 tool update
    • Changedbyte_buy_data3 fields changed
      • changedInput schema / properties / body / description
        Previous value: -"Optional JSON query body for POST oracles. Supplying it switches the call from GET to POST. Required by the verdict oracles, e.g. address-reputation {domain,address[,amount,chain]}, sanctions-screen {address|name}, pkg-verdict {ecosystem,package[,version]}, reasoning-verdict {subject}. Omit for GET data feeds (weather, defi-yields, …)."New value: +"Optional JSON query body for POST oracles. Supplying it switches the call from GET to POST. Required by the verdict oracles, e.g. address-reputation {domain,address[,amount,chain]}, sanctions-screen {address|name}, pkg-verdict {ecosystem,package[,version]}, reasoning-verdict {subject}. Omit for GET data feeds (weather, earthquakes, …)."
      • changedInput schema / properties / feed / description
        Previous value: -"Feed slug — one of: defi-yields ($0.030), weather ($0.0050), earthquakes ($0.0030), space-weather ($0.0030), news-feed ($0.010), code-pulse ($0.020), runtime-eol ($0.020), threat-intel ($0.050), x402-pulse ($0.010), stablecoin-rails ($0.030), perp-funding ($0.020), usc-statute ($0.050), evidence-pack ($0.100), address-reputation ($0.100), pkg-verdict ($0.100), sanctions-screen ($0.100), reasoning-verdict ($0.100), liquidation-stream ($0.030), positioning-snapshot ($0.030), agent-compute ($0.050), agent-memory ($0.050), agent-tools ($0.050). Full catalog: https://x402.payperbyte.io/feeds (free GET). (For fact-oracle Q&A use byte_query_fact instead — it uses a different request-response flow.)"New value: +"Feed slug — one of: weather ($0.0050), earthquakes ($0.0030), runtime-eol ($0.020), threat-intel ($0.050), evidence-pack ($0.100), address-reputation ($0.100), pkg-verdict ($0.100), sanctions-screen ($0.100), reasoning-verdict ($0.100), liquidation-stream ($0.030), positioning-snapshot ($0.030). Full catalog: https://x402.payperbyte.io/feeds (free GET). (For fact-oracle Q&A use byte_query_fact instead — it uses a different request-response flow.)"
      • changedOutput schema / properties / price / description
        Previous value: -"USDC paid for this packet (e.g. '$0.001000'); omitted on free feeds"New value: +"USDC paid for this packet (e.g. '$0.003000'); omitted on free feeds"

Related MCP Connectors

Related MCP Servers

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.