Updates one shared beta prior with each variant’s supplied clicks and non-clicks, reports posterior means and bounded normal-approximation 95% intervals, and ranks by posterior mean. It does not run an experiment, correct assignment bias, prove significance or predict future performance under distribution shift.

Tokenizes caller-supplied campaign and trend keywords, calculates overlap relative to the trend vocabulary, and flags any supplied blocked keyword. It neither discovers live trends nor recommends deception, impersonation or spam; its scoped purpose is a transparent relevance and brand-safety screen.

Weights likes, comments, shares, saves and clicks, divides by supplied reach, and reports cohort and aggregate points per thousand reached accounts. It does not access a platform, distinguish authentic from manipulated activity, measure sentiment or predict revenue.

Marine meteorological and oceanographic conditions database. Access high-resolution daily projections for wave heights (max, wind waves, swells), wave directions, ocean wave periods, and dominant sea surface swells for coastal or open ocean locations. Critical for shipping route optimization, marine construction, surfing forecasting, and coastal geointelligence.

SEC Form 13F filings data showing institutional investment manager holdings. Form 13F is required to be filed quarterly by institutional investment managers with at least $100 million in qualifying assets under management. Can't find what you're looking for? POST feedback to /feedback, no charge.

Japanese postal-code lookup and reverse lookup. Keywords: Japanese postal lookup, Japan Post postal code, postal code reverse lookup, 日本郵便番号検索. Use a postal code or prefecture/city/ward/town components against the local Japan Post snapshot. / 通过邮编或都道府县、市区町村、区、町名字段，在本地 Japan Post 数据中进行日本邮编反查。

Agent Decision Signal. Market intelligence for autonomous AI agents deciding what emerging agent-economy opportunity, infrastructure trend or research signal to investigate, build, monitor or deprioritize next. Returns a deterministic action with confidence, evidence, freshness, next action, stop conditions and provenance.

What a Base transaction costs right now, with the RPC provider and trust level behind the number, so a caller can tell a credentialed reading from a degraded one before pricing a transaction.

Give this API a link to any website's sitemap.xml file and it will fetch and parse it, returning every URL found inside. If the sitemap links to other sitemaps (called sitemap indexes), it will follow and extract those too. Each URL is returned with any extra information available, such as when the page was last updated and how often it changes. Useful for SEO audits, content inventories, broken link checks, and competitive research.

ChainQuery Bitcoin Intelligence: independent Bitcoin-native on-chain data over x402, no API key. Top 10 addresses by balance from the weekly UTXO-set snapshot, with labels.

Word, sentence, and paragraph counts, reading time, and readability score for text.

USD price for major tokens by symbol or any Base ERC-20 by contract address, with source failover.

Official PTAX USD/BRL exchange rate (the reference rate used in Brazilian contracts). Central Bank of Brazil.

Cross-venue funding arbitrage signal from real-time 8h-equivalent funding rates on up to 6 venues (Binance, OKX, Bybit, KuCoin, Bitget, Hyperliquid). Returns the gross and net-of-fees spread between the best short venue and best long venue (gross_spread_bps, net_spread_bps after a 20 bps round-trip fee estimate), spread_8h_normalized, venues_count, per-venue rates with funding_interval_hours, annualized_pct, and an actionability label. All 17 assets. $0.02 USDC via x402.

Use before a coding agent installs an unfamiliar npm dependency. Returns current facts from the official npm registry: the version `npm install` resolves (dist-tags.latest), prerelease and deprecation status, engines.node compatibility with an optional target Node version (real SemVer evaluation), license, days since release, best-effort weekly downloads, repository URL and maintainer count. Facts only — no safety, trust, or malware verdict.

Retrieves a complete list of available vault categorization tags that can be used for filtering and organizing vault data

Audit a whole dependency manifest in one call before installing or upgrading. Send a package.json, a requirements.txt, or npm and PyPI package lists (up to 50 packages). Per dependency: latest version and publish date, whether your pin is behind, license, deprecation or yanked status, weekly npm downloads, and known vulnerabilities from OSV with severity and first fixed version. Deterministic, no LLM. Use before adding or bumping deps or when reviewing a lockfile change.

Give it a longitude and latitude inside the United States and it answers with the Census FIPS codes for that point: the 2-digit state code, the 5-digit county GEOID, and the GEOID of the congressional district. Parameters go in the query string: this is a GET, there is no body. The codes are the product and the names are a courtesy. A county GEOID is the join key to essentially every geography-keyed federal dataset -- the American Community Survey, BLS Local Area Unemployment Statistics, BEA regional accounts, CDC WONDER, HUD, USDA, FEMA -- and the state code is its first two digits, so one call gives you both keys already in the form those tables expect. County GEOID is also the first five digits of a tract GEOID (11 digits) and of a block group GEOID (12), so it is the prefix you would filter a tract-level extract down with. COVERAGE, stated up front because the shortfall is the point: this endpoint answers state, county and congressional district, and it does NOT answer tract, block group, place or ZCTA. That is a size limit, not an oversight, and it was measured rather than guessed. A national compacted H3 index of tracts is 3196 KiB gzipped and of block groups 5335 KiB, at a resolution already too coarse for either; the whole Worker has 3 MiB compressed to spend and most of that was gone before this route existed. Those four tiers need an object store behind the Worker and will arrive with one. Every response repeats this under `coverage`, so an agent never has to infer it from a missing field. In the meantime geocoding.geo.census.gov answers all seven tiers, free, authoritative, at the cost of a round trip and a dependency. VINTAGE: TIGER/Line 2025, congressional districts for the 119th Congress. It is on every response under `vintage` and it matters more here than almost anywhere else in this catalog, because TIGER is re-cut annually and districts move with redistricting, so a stale district code is a wrong answer a caller cannot detect from the outside. Nothing here self-updates; a new vintage means a rebuild. The data is a work of the United States government and is in the public domain (17 U.S.C. 105) -- no attribution clause and no redistribution terms. ACCURACY, and this is the part to read before you trust a code. The boundaries themselves are full-resolution TIGER, the same geometry the Census Geocoder answers from, not a simplified copy. What is approximate is the lookup: the polygons are indexed as compacted H3 cells at resolution 7, about 1.22 km across, so a point within roughly 610 m of a boundary may be attributed to the neighbour. County equivalents and districts too small to describe at that resolution -- Falls Church city, the other Virginia independent cities, the congressional districts inside New York City -- carry a second index at resolution 9, about 87 m, and `boundaryAccuracyMetres` says which one answered you. Because a 610 m index is only useful if you know when not to trust it, every response carries `boundaryUncertain.county` and `boundaryUncertain.congressionalDistrict`. They are true when a neighbouring cell resolves to a different code, which means the boundary is close enough that the index cannot settle which side you are on. Measured against geocoding.geo.census.gov on 650 coordinates: on 400 population-weighted points the county code was right 389 times and the district code 383, and every one of the 11 and 17 disagreements was flagged; on 250 points drawn deliberately 100 m to 1500 m from a county line the county code was right 183 times, and every one of the 67 wrong county codes and 25 wrong district codes was flagged. Across all 650 it never returned a wrong code with the flag clear. It is generous in the other direction -- it flagged 74 of the 400 correct-heavy sample -- so treat `true` as "verify this one if it matters" rather than as "this is wrong". Outside the United States the answer is `found: false` with null codes and a paid 200, because "this coordinate is not in the US" is the answer you asked for. County polygons include their legal water area out to the three-mile limit and across the Great Lakes, so harbours, piers and lake coordinates resolve normally and only genuinely foreign or high-seas points fall out. Coverage is the 50 states, DC, Puerto Rico, American Samoa, Guam, the Northern Mariana Islands and the US Virgin Islands. A small amount of water is inside a county but inside no congressional district, which TIGER publishes as a real polygon; that answers with a district whose number is null rather than with a guess. 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. TIGER publishes in NAD83, which this reads as WGS 84; the two differ by under two metres, which is a fortieth of the index's own resolution.

Check npm packages before you install or upgrade. Send {"packages":["lodash@4.17.20","express"]} or a package.json (dependencies and devDependencies), up to 50 packages. Per package: latest version and publish date, whether a pinned version is behind, license, deprecation notice, weekly downloads, and known vulnerabilities from OSV with severity and first fixed version. Deterministic registry data, no LLM.

Add or subtract N Japanese business days from a date (e.g. settlement date T+2, delivery ETA). Skips weekends and national holidays; optional bank calendar.