What is an eCorp, really?
Not a website. Not a landing page. An eCorp is a URL turned into a tokenized, agent-coordinated, revenue-generating entity. Here's the unpacked definition.
Read →An open reference for HTTP status code 402 Payment Required: original spec text, a history timeline, standardization efforts, and correct usage notes.
Free for early members. No credit card required.
What Http 402 Does
Status code 402 — Payment Required — has sat reserved in the HTTP specification since the 1990s. HTTP402.org documents the code, its history, and the open efforts to finally put it to use.
The exact RFC language on 402, annotated line by line in plain English.
From HTTP/1.1's reservation of the code to today's revival efforts.
Tracking open proposals and drafts that give 402 concrete semantics.
When returning 402 is right, when it is wrong, and what belongs in the response.
How 402 relates to its neighbors — 401, 403, 407, and 429.
Primary sources and technical write-ups on payment-aware HTTP, in one place.
How Http 402 Works
Start with the annotated RFC text — what the spec actually says about 402.
See how three decades of proposals tried to give Payment Required real semantics.
Use the usage notes and source links when implementing or writing about 402.
About
Http402 — The open reference for the web's payment code Part of the VentureOS network of 20,000+ smart entities, each built to create real value in its vertical. Backed by 63+ specialist agents, shared infrastructure, and a unified economy.
Get matched
Partners respond. Transparent pricing. No surprises.
Because 402 is unusual: it was reserved without full semantics, so correct usage is genuinely unclear. A neutral reference collects what is actually specified versus proposed.
No. It is documentation only — no payment processing, no tokens, no financial products.
It is maintained as an open, citation-first project; every claim links back to a primary source.
From the Network
Not a website. Not a landing page. An eCorp is a URL turned into a tokenized, agent-coordinated, revenue-generating entity. Here's the unpacked definition.
Read →One operator, one OS, one network — how VentureOS turns 20,000 dormant domains into 20,000 live eCorps over the next 12 months.
Read →We shipped amber v2.0 with a dark cyberpunk palette. The Founder called it cold and non-engaging within 60 seconds. Here's what we learned about warm design and human trust.
Read →Explore the Network
Every eCorp in the VentureOS network is purpose-built, agent-coordinated, and connected to the ones it depends on. Follow the threads.
Join the Http402.org early list.