Spot price: the on-chain DEX price for SOL, BTC or ETH, the median of deep USDC pools on Solana, Ethereum and Base read from chain state, and the pools that served it. Use when you need to answer: What is the spot price, without picking a venue? Any other symbol answers 400 with the supported list and is never billed.

Batch KYA Trust Score analysis for up to 50 AI agent or wallet addresses in one call. Returns a per-address 7-component trust score (0-100), risk tier, and sanctions status.

Fetch GitHub data from a ref (repo + README, files, commits, PRs, issues, discussions)

Highest-yield DeFi pools across every chain and protocol, filterable by chain, project, or asset symbol: each pool returns TVL in USD, total APY with base/reward split, stablecoin flag, impermanent-loss risk, and exposure. Sort by APY or TVL, and set sustainable=true to exclude IL-risky pure reward-emission farms. Find where to earn yield on USDC, ETH, SOL and more. Sourced from DefiLlama.

Prueft die IBAN nach ISO 13616 und ISO 7064 mit Pruefsumme mod 97-10 gegen die Laengentabelle von 74 Laendern, zerlegt die BBAN fuer elf Laender in Bankleitzahl und Kontonummer, meldet SEPA-Zugehoerigkeit und prueft eine mitgegebene BIC auf Format und Landesgleichheit. Trifft keine Aussage zu Existenz oder Deckung.

The current chain tip (latest block height) via eth_blockNumber, across Base, Ethereum, Optimism, Arbitrum, Polygon, Gnosis. The freshness read settlement, indexing and trading agents poll to know where the chain is. Live public RPC; one paid call. List your own x402 service on bazaar.agentexchange.work/listings: 1 USD, 30 days, live at once, no account.

Real-time SOL/USD price feed oracle. Retrieves live spot rate, 24h high/low, and volume directly from Coinbase Exchange.

Counts zeros, ones and runs, reports a normalized monobit imbalance, and compares observed runs with the IID Bernoulli expectation. It generates no random number and is not a NIST test-suite replacement, entropy estimate or certification of cryptographic randomness.

Fetch a web page and extract clean content

Vorwärts- und Rückwärtsgeokodierung mit normalisierter Adresse (Straße, Hausnummer, PLZ, Ort, Bundesland, Land) und Ergebnis-Cache. Kein Schlüssel, kein Konto.

Recent news headlines for any company, topic or query: deduplicated titles with source, link and publish date from a broad news index. Window configurable 1-30 days. JSON response. $0.01 USDC per call, pay via x402, no API key.

Offline validator for a Romanian CUI (company tax ID). Strips an optional 'RO' prefix, applies weights 7-5-3-2-1-7-3-2 to the digits preceding the check digit (right-to-left), sums the weighted products, multiplies by 10, takes mod 11 (mapping a remainder of 10 to 0), and compares the result to the supplied check digit.

Check whether demand for a Solana token is manufactured before you buy: the organic score standalone — what share of volume is real buyers and sellers versus manufactured, plus organic buyers, trades-per-trader and the vol/liq ratio with the wash verdict. The demand-authenticity probe that complements a pre-trade safety check. — $0.01 USDC

Offline validator for a Swedish Organisationsnummer (company registration number). Normalizes input to 10 digits (accepts XXXXXX-XXXX or plain), checks length/digit-3 validity, and verifies the final check digit using the Luhn (mod 10) algorithm.

Fits reference = slope × observed + offset with ordinary least squares over paired caller-supplied readings. It reports residual diagnostics and does not claim traceability, uncertainty accreditation or suitability beyond the supplied calibration range.

Offline validator for a Danish CVR-nummer (8-digit business registration number issued by the Danish Business Authority). Normalizes input to digits only, checks length and computes a modulus-11 checksum using weights 2,7,6,5,4,3,2 on the first 7 digits compared against the 8th check digit. Result is flagged as best-effort since some legacy CVR numbers do not conform to the checksum rule.

Historical weekly Stock Trends indicator series for a symbol. Stock Trends indicators are part of a multi-decade classification framework with records extending back to 1980. Their value comes from consistent semantics across market history: trend state, trend persistence, relative performance, relative performance direction, and volume activity are encoded in a stable doctrine designed for longitudinal research.

Get a paginated timeline of replies from an X user.

Computes cohort median, median absolute deviation and robust z-scores for one numeric reading per device. A caller-selected threshold determines flags. It detects cross-sectional outliers only and does not diagnose root cause or learn temporal behavior.

Give it a longitude and latitude and it answers with the IANA timezone identifier (America/New_York), the UTC offset in force there right now, whether daylight saving is currently in effect and by how much, the local wall-clock time, and the zone's standard offset. Pass an optional ISO 8601 `at` instant to ask about any moment between 1900 and 2100 instead of now, which is what you want when scheduling something months out across a DST boundary. Parameters go in the query string: this is a GET, there is no body. Two halves, with different vintages, and the difference matters. The offset and the DST rules come from the runtime's own timezone database and are current: a rule change reaches this endpoint when Cloudflare updates ICU, with no redeploy here. The *boundaries* come from tz_world (efele.net), CC0 1.0 and derived from VMAP0, a public-domain US government product. That map was frozen at tzdb 2016d in May 2016, and this catalog sells public-domain and permissively-licensed data only, which is why it is used rather than the current OpenStreetMap-derived alternative. What the vintage costs, measured against IANA's own coordinates for all 312 zones in zone1970.tab rather than estimated: 293 agree. Of the 19 that do not, 7 are Antarctic research stations, which this map does not cover at all and which fall back to the open-water rule; 7 more return a different identifier for the identical offset and DST all year (Australia/Brisbane for Australia/Lindeman, America/Regina for America/Swift_Current, and five like them), so the time is right and only the name is old. That leaves four regions where the answer is up to one hour wrong because the zone was split after 2016: Chilean Magallanes and Aysen (answered as America/Santiago rather than America/Punta_Arenas or America/Coyhaique), the Mexican border municipalities around Ciudad Juarez, Saratov Oblast in Russia, and the weeks each spring when Asia/Hebron and Asia/Jerusalem change on different dates. If you query inside one of those, do not trust this endpoint. Boundary precision is a separate question from vintage. The map is indexed as compacted H3 cells at resolution 6, whose half-width is about 1.6 km, chosen to match VMAP0's own stated positional accuracy of roughly 2 km rather than to flatter the index. So a point within a couple of kilometres of a zone border may be attributed to the neighbour, and no amount of the source's precision would fix that because the source does not have it. Away from a border the answer is exact. Every answer says where it came from under `source`. `boundary` means the point is inside a mapped timezone polygon and is the answer you are paying for. `coastal` means it is over water or on land this map does not cover, and the identifier is the nearest zone within about 60 km -- correct for a harbour or a coastal city whose coordinate falls just offshore, and not a boundary result. `nautical` means open water more than about 60 km from mapped land, answered with the tz database's own rule for international waters, meridians 15 degrees apart; it is not the time kept aboard any vessel and it ignores territorial waters. Longitude and latitude are checked against EPSG:4326 bounds before anything else touches them, because H3 silently normalises an out-of-range latitude into a real but wrong cell rather than refusing it. Reproject with POST /v1/transform first if you are not already in WGS 84. The DST flag is decided on offsets rather than on the tz database's own isdst bit, so Europe/Dublin reads as daylight saving in summer like everywhere else, and it is measured over a window either side of the instant so that a zone which changes its standard offset mid-year -- Asia/Almaty in 2024 -- is not mistaken for one on daylight saving.