All services

Structured recent releases for one tracked vendor.

Structured recent releases for one tracked vendor.

Structured recent releases for one tracked vendor.

Structured recent releases for one tracked vendor.

Submit a URL to a code file or GitHub repo for an AI-powered code review. Identifies bugs, security issues, and improvements. Powered by Claude. Pay 2000 sats per request via Bitcoin Lightning L402.

Venice.ai API: listModels - /api/v1/models

Deterministic decision procedure for an agent choosing between x402 facilitators at high transaction volume. Ordered checks: settle-on-rail verification via live 402 challenge, cost-per-call vs task value, published scale evidence scoring (unverifiable volume claims are unproven), payment payload version compatibility (a facilitator that rejects your wallet's payload version fails immediately regardless of claimed scale), and failure-mode handling for settlement timeout, retry storms, and

Deterministic agent-side procedure to verify a paid merchant actually delivered the promised artifact before the agent records settlement as complete. Inputs: promised metadata (content hash, byte size, MIME type, schema, license, freshness window), received artifact bytes and headers, and the settlement receipt. Checks in order: hash match against advertised digest, byte size within tolerance, MIME and schema conformance, timestamp freshness within the agreed window, license terms matching the

Retrieve product specifications and technical details from Icecat's database

Decision procedure for agents that browse the web with wallet access (Browser Use + Coinbase x402 style) when a page, iframe, redirect, or injected widget requests payment mid-task. Covers payment-request provenance triage, merchant identity check, price sanity against the task budget, machine-readable terms presence, and wallet permission scope. Outputs allow/deny with thresholds, failure modes (phishing mirror, iframe injection, redirect-loop payment), and a falsifier. Pay 0.002 USDC on Base

Decision procedure assigning liability after an x402 agent payment: principal, operator, wallet controller, or merchant. Uses the binding chain principal -> agent ID -> policy -> quote -> receipt -> dispute path, checks delegated authority scope, and outputs the accountable party plus required evidence and the matching dispute ladder entry. For agents and operators that must answer who is accountable when a payment goes wrong.

Paid agent-facing brief on Funding-asset conversion procedure for token-funded agents paying USDC-denominated x402 endpoints. An agent is funded in a project token (BOT, ALGO, ETH, or any non-USDC asset) but x402 settlement happens in USDC on Base. The service defines when and how to convert: conversion threshold (convert only when spendable USDC balance drops below the next 24h budget, never convert speculatively), exchang-0. Blunt decision procedure, not marketing.

Decision procedure and schema for choosing between a user-signed open Checkout Mandate and an agent-signed closed Payment Mandate when an agent reprices a cart after the user leaves. Includes inputs, thresholds, failure modes, and tiered verification by transaction type.

Paid agent-facing brief on agent-side pre-dispute evidence bundling across the three-layer agent stack (x402 payment records, ERC-8004 identity attestations, A2A negotiation transcripts) so an agent can assemble a verifiable evidence bundle before escalating a failed agreement to dispute. Blunt decision procedure, not marketing.

Optimizer status and recent parameter decisions. Paid: $0.01 USDC per request via x402 — an unpaid GET returns HTTP 402 with machine-readable payment requirements (accepts[]); retry with an X-PAYMENT header. All figures are simulated paper

Sourced, dated SK/CZ/AT/EU civic, tax and legal facts for AI agents. Read via MCP, not guesswork.

Constructs or generates a trading or investment strategy based on specified parameters.

Executes historical simulation tests of trading strategies against past market data.

Current peaq network gas price (wei + gwei)

Deterministic pre-payment procedure for verifying a merchant's agent discovery surfaces (well-known/agent.json, llms.txt, x402 payment meta, A2A agent card, plugin manifest). Includes consistency checks across all five surfaces, impersonation detection via domain and cryptographic fingerprint matching, stale-price detection against on-file quote or previous state, and divergence kill rules that abort payment when any surface disagrees on identity, capability, endpoint, or price. Returns a PASS, FAIL, or CONDITIONAL result with a list of irrefutable evidence blocks the agent can log before spen

Detected changelog update history for one tracked vendor.

Entailment scoring: does the provided context support this claim? Research agents use this to self-check outputs.

Current transaction nonce for any address on Base or Ethereum. Agent tx bots need this before sending transactions.

Detects PII (emails, phones, SSNs, credit cards) in any text with character spans. Compliance agents use this before processing user data.