APIs.io · weekly traffic

Three measurement layers

The CDN edge, a browser beacon, and agent fetches of the markdown twins. They count different populations, and the distance between them is the finding — not an error to reconcile.

Week of 2026-10-12 → 2026-10-18
42 weeks tracked · collected 2026-10-19
What we measure success by · week of 2026-10-12 → 2026-10-18

Almost everything that reaches APIs.io is a machine, so traffic below is context, not the goal. These two are the numbers that matter: companies asking to have their APIs listed, and people signing up for API access.

New APIs submitted
44
55 the week before · 431 since July
Unique providers submitted through apis.io/add, counted once, the week first seen, renames collapsed, delistings removed.
API signups
89
101 the week before · 706 since July
New accounts on the APIs.io developer portal.
Week endingNew APIsSignups
2026-10-18 44 89
2026-10-11 55 101
2026-10-04 48 92
2026-09-27 31 97
2026-09-20 31 89
2026-09-13 27 66
2026-09-06 46 66
2026-08-30 31 82
2026-08-23 23 22
2026-08-16 15 0
2026-08-09 23 0
2026-08-02 17 1
2026-07-26 11 0
2026-07-19 29 0
2026-07-12 0 0
2026-07-05 0 1

new_apis = unique canonical provider slugs submitted through apis.io/add, counted in the week first seen, collapsed through renamed.yml, minus delisted; S3 records until 2026-09-21, the support-queued harvest backlog after. signups = API sign-ups by signed_up date. Calendar weeks, Mon-Sun. Data: intake_weekly.json.

AI share of twin fetches
31.1%

61,650 of 198,401 markdown-twin fetches last week came from named AI crawlers. The same bytes go to every client — nothing here varies by user-agent.

A further 83,030 fetches came from clients presenting an ordinary browser user-agent. Humans do not hand-fetch index.md, so the AI share is a floor, not a ceiling.

Edge · CloudFront
14,046,329
▲ 11%vs prior week
Every request the CDN served — pages, assets, /api, /mcp, bots alike. 432 GB, 16.23% 4xx/5xx.
Browser · GA4
476,405
▲ 157%vs prior week
Page views from JavaScript-executing clients only. Read the signal check below before quoting this.
Agent · markdown twins
198,401
▼ 38%vs prior week
Read from CloudFront access logs. Counting began 2026-08-13; earlier weeks were never measured.

What the browser layer is actually counting

Four indicators read together, not as separate stats. Each one alone is survivable; all four at once is a bot signature.

Not an audience number
Sessions from one geography flag
80.5%
Singapore, 376,300 of 466,983 sessions.
Bounce rate flag
97.5%
One page, no second action, on the overwhelming majority of visits.
Average session flag
7s
Too short to read a heading, let alone a provider profile.
New users flag
98%
Effectively nobody returns, week after week.
Venue is not operator. Singapore leads the country table, but CloudFront logs for 2026-08-13 resolved Singapore-edge client IPs to Tencent 34.0%, CacheFly 6.9%, China Unicom, China Telecom and Alibaba — plus a rotating-user-agent fleet running exactly 15 user-agents per IP. Registry country says Singapore; the operators are elsewhere. Country here is where traffic egressed, never where anyone sat.

Daily volume by layer

One shared timeline, one scale per layer. The three differ by orders of magnitude, so plotting them against a common axis would invent a relationship that is not in the data.

Edge requests
Browser page views
Agent twin fetches

The shaded band on the agent panel is time that was never measured. Twin counting began 2026-08-13, when CloudFront access logging was switched on — which is not the same as nobody having come.

Who is fetching

Ranked by fetches of the markdown twins, last week. Search and SEO bots are shown but excluded from the AI share.

Fetchers by user-agent

15 distinct agents, from 19,573,055 logged requests scanned.

browser 83,030
other-bot 43,683
meta-externalagent AI 23,494
gptbot AI 14,662
oai-searchbot AI 8,807
amazonbot AI 8,107
bingbot 7,273
claudebot AI 3,101
applebot AI 3,020
other 2,752
Counted as AI Search, SEO, unattributed

How they crawl

The shape of the crawl, not a leaderboard.

Markdown served to agents last week — 4 KB per fetch, identical bytes for every client. 801 MB
Share held by the single most-fetched twin (130 fetches). There is no head — agents are crawling broadly, not hammering a few pages. 0.06%
Largest single day, 2026-08-21 — 69% of that entire week arrived in 24 hours. One crawler sweeping the catalog, not a trend. 100,866

Weekly history

An em dash means not measured, never zero. Twin counting began 2026-08-13; printing 0 for the weeks before it would assert that no agent came, which we do not know.

Week ending Requests GB Err Views Sessions SG % Bounce Twins AI %
2026-10-18 14,046,329 432 16.23% 476,405 466,983 80.5% 97.5% 198,401 31.1%
2026-10-11 12,625,930 318 14.65% 185,220 177,925 70.7% 93.3% 318,223 55.3%
2026-10-04 9,523,358 297 7.37% 136,051 128,788 62.8% 91.6% 126,167 66.2%
2026-09-27 8,281,659 266 8.67% 145,672 137,769 70.7% 92.1% 176,034 50.9%
2026-09-20 6,521,515 226 14.91% 145,476 140,065 69.5% 92.0% 93,639 55.4%
2026-09-13 7,517,263 205 15.3% 116,771 112,170 69.1% 91.0% 136,024 79.2%
2026-09-06 7,294,109 226 17.6% 132,063 129,940 65.0% 88.9% 94,514 73.8%
2026-08-30 9,095,343 265 15.13% 222,848 219,643 62.4% 95.1% 83,469 73.2%
2026-08-23 7,831,319 281 6.78% 196,720 188,855 50.9% 95.3% 145,637 81.6%
2026-08-16 6,479,429 187 8.77% 213,379 206,851 66.0% 95.4% 6,322* 59.2%
2026-08-09 6,561,545 159 14.28% 104,859 101,108 34.1% 96.0% — —
2026-08-02 9,548,627 196 16.49% 526,240 502,881 83.9% 83.8% — —
2026-07-26 6,373,099 122 10.55% 124,539 95,693 39.5% 92.8% — —
2026-07-19 5,218,191 75 5.21% 111,200 103,870 16.3% 89.8% — —
2026-07-12 6,018,956 71 5.48% 123,654 115,883 20.3% 91.3% — —
2026-07-05 6,515,760 69 9.48% 229,654 222,191 55.4% 95.4% — —
2026-06-28 5,363,220 77 5.28% 161,481 152,684 25.7% 91.3% — —
2026-06-21 1,320,865 17 15.3% 75,183 70,441 6.1% 88.6% — —
2026-06-14 2,073,492 57 — 58,598 54,197 9.4% 88.8% — —
2026-06-07 — — — 26,405 24,451 14.1% 89.0% — —
2026-05-31 — — — 12,471 11,699 90.1% 96.8% — —
2026-05-24 — — — 4,515 3,533 64.3% 79.1% — —
2026-05-17 — — — 15,323 14,981 95.8% 98.9% — —
2026-05-10 — — — 840 385 16.1% 67.5% — —
2026-05-03 — — — 1,478 1,032 76.1% 91.7% — —
2026-04-26 — — — 978 708 68.2% 91.8% — —
2026-04-19 — — — 690 375 21.0% 76.8% — —
2026-04-12 — — — 434 252 15.8% 67.9% — —
2026-04-05 — — — 239 186 19.8% 73.1% — —
2026-03-29 — — — 246 213 15.4% 69.5% — —
2026-03-22 — — — 372 254 20.4% 72.4% — —
2026-03-15 — — — 511 361 16.8% 75.1% — —
2026-03-08 — — — 430 322 13.0% 69.9% — —
2026-03-01 — — — 785 454 24.4% 74.7% — —
2026-02-22 — — — 912 490 21.0% 76.5% — —
2026-02-15 — — — 763 412 13.5% 72.1% — —
2026-02-08 — — — 566 383 — 76.5% — —
2026-02-01 — — — 428 358 — 80.2% — —
2026-01-25 — — — 517 378 — 73.0% — —
2026-01-18 — — — 312 267 1.4% 76.0% — —
2026-01-11 — — — 579 370 — 74.1% — —
2026-01-04 — — — 897 318 — 79.6% — —
42 weeks · newest first

Why the numbers differ

Edge counts everything

  • Every HTTP request served — pages and every asset (CSS, JS, images, fonts)
  • Bots, crawlers, feed readers, and /api + /mcp clients
  • Cached responses served at the edge, which never reach the S3 origin
  • Anything that loads before JavaScript runs, and clients with JavaScript off

Browser counts a subset

  • Fires only when JavaScript loads and executes successfully
  • Ad blockers and privacy extensions suppress the tag — heavily, on a developer audience
  • Declared bots are filtered automatically; headless browsers are not
  • Carries no source or medium, so it cannot attribute a visit to anything

Agents are invisible to both

  • Agents execute no JavaScript, so the browser layer reports zero for them no matter what happens — a gap no tag fix closes
  • The edge counts the request but cannot tell a twin fetch from any other hit, which is why this number comes from the access logs
  • A twin fetch has no click-through and never will, so it is reported on its own and never blended into a rate beside human traffic
  • The same bytes go to every client. Nothing here varies by user-agent, which is the whole point on a network that publishes the tool auditing that behavior