Directory / 2s.io
2s.io/api/dev/rfc working
https://2s.io/api/dev/rfc
Before you pay
- Advice
ok- Protocol
- x402 · http · GET
- Asks for
- 0.003 USDC on base
- Catalogue says
- 0.003 USDC
- Pays to
0x2b6D4988Db4723E6908Db86Ab2b8dFBc51FC32C5- Last check
- 13 min ago · 213 ms · HTTP 402
- Detail
- 402 with valid terms
Reliability
- Uptime 24 h
- 100.0% (39 checks)
- Uptime 7 days
- 100.0% (270 checks)
- Uptime, 9 days observed
- 100.0% (signed daily)
- Listed by
- x402-bazaar
- First seen by alalanet
- 2026-11-05 22:11 UTC
Trust Score
80 of 95
Open formula: /trust. Recomputed once a day from what alalanet observed and its sources publish; nothing here can be bought.
Payments
- Read on chain by alalanet
- 1,694 payments from 49 wallets, $8.75USDC on Base into this address since 2026-10-15; alalanet's own test wallet excluded
- Repeat payers
- 24 paid on two or more days
- Largest payer
- 42.6% of the payments
- Independent payers
- 49 of 49 countedalalanet read the wallets of the 10 largest payers: 0 funded by the seller, not counted; 0 joined to another payer (funded by it, or by the same address within 72 hours before both paid); 3 first funded within 72 hours before paying
This listing was first seen on 2026-11-05; payments before that day may be missing, so the figures are a lower bound.
- Catalogue says
- 211 calls from 4 payers in 30 daysthe catalogue's own counter (x402 Bazaar), not checked by alalanet
- Buyers' reports, 30 days
- 1 delivered, 0 partial, 0 not delivered or wrongdeliveries reported by 1 wallet, failures by 0; each report is bound to a payment on chain; alalanet's own test purchases are counted here and add no points
- alalanet's test purchase
deliveredon 2026-11-12: HTTP 200, 888 bytes, transaction0x9c15c10d9c019c348f93de6b2f932aba17b3e90ae0d42f45f63e0fec56be646da capped purchase from alalanet's own wallet; shown as a fact, adds no points
Description (from the catalogue, unverified)
Look up an IETF RFC by number. Pass number as RFC2616, 2616, or the integer 2616. Returns the RFC title, authors, publication date, status (e.g. INTERNET STANDARD, PROPOSED STANDARD, DRAFT STANDARD, INFORMATIONAL, EXPERIMENTAL, HISTORIC, BEST CURRENT PRACTICE), stream (IETF/IAB/IRTF/Independent/Legacy), DOI, canonical rfc-editor.org URL, and the full standards relationship chain: which RFCs this one obsoletes / is obsoleted by, and which it updates / is updated by. Authoritative data from the IETF/RFC Editor index. Use this to resolve whether a spec is current or superseded before relying on i…
Signed history
| When | Statement | Log index |
|---|---|---|
| 2026-11-14 00:19 UTC | ddea5b4d…41cbb6 daily summary | 712083 |
| 2026-11-13 00:16 UTC | 6d554537…7ae386 daily summary | 634500 |
| 2026-11-12 07:10 UTC | 0edb731e…716dd1 purchase report | 571538 |
| 2026-11-12 00:19 UTC | 916f2c94…1a4790 daily summary | 556043 |
| 2026-11-11 00:19 UTC | 362d15d3…9f808e daily summary | 475502 |
| 2026-11-10 00:18 UTC | e8348713…196c97 daily summary | 393065 |
| 2026-11-09 00:17 UTC | a1691821…aeff3a daily summary | 301700 |
| 2026-11-08 00:14 UTC | a443db68…7bee6e daily summary | 223484 |
| 2026-11-07 00:17 UTC | e271ba9c…e86e40 daily summary | 144657 |
| 2026-11-06 00:14 UTC | 27b99e91…376dab daily summary | 52496 |
Verify any statement offline: how.
For agents and owners
JSON: https://alalanet.com/v1/services/ts5elll6ys4a5ygx
Badge:
<a href="https://alalanet.com/s/ts5elll6ys4a5ygx"><img src="https://alalanet.com/badge/ts5elll6ys4a5ygx" alt="alalanet status"></a>Own this service? Claim it (free). Do not want it checked? See the prober page.