







The Fetch standard defines requests, responses, and the process that binds them: fetching.
Fetch Is Not Enough
The Fetch API gave JavaScript runtimes a shared vocabulary for HTTP. But HTTP has capabilities that Fetch can't express, and every runtime has diverged trying to work around the gaps.
Standard Search
A search engine for standard.site posts, indexing documents published on AT Protocol.

Introduction · Standard Reader
Build on Standard — an open reading network on the AT Protocol. What the developer docs cover.
How to Read an RFC
Requests for Comments (RFCs) are how we specify many protocols on the Internet. These documents are alternatively treated as holy texts by developers who parse them for hidden meanings, then shunned as irrelevant because they can’t be understood. This often leads to frustration and – more significantly – interoperability and security issues. However, with some insight into how they’re constructed and published, it’s a bit easier to understand what you’re looking at.

What is Standard Site, and why is it useful? - Leaflet Lab Notes
Lab Notes 029: explaining how Standard Site works, how it compares to RSS, and its utility for readers and publishers
standards.group
standards.group — a forge for specs. Write, version, and publish specifications from your own AT Protocol account.
HTTP Requests | Grafana k6 documentation
Define the HTTP requests and methods you want to use. k6 adds tags to the requests, making it easier to filter results. You can customize tags as you wish.

HTTP Semantics
The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for distributed, collaborative, hypertext information systems. This document describes the overall architecture of HTTP, establishes common terminology, and defines aspects of the protocol that are shared by all versions. In this definition are core protocol elements, extensibility mechanisms, and the "http" and "https" Uniform Resource Identifier (URI) schemes. This document updates RFC 3864 and obsoletes RFCs 2818, 7231, 7232, 7233, 7235, 7538, 7615, 7694, and portions of 7230.
Lexicons · Standard Reader
Published app.standard-reader.* record schemas for reader repo state.
AT Protocol Handler - Chrome Web Store
AT Protocol utilities: handle tools, post filtering, PDS info.
Protocol Buffers
Protocol Buffers are language-neutral, platform-neutral extensible mechanisms for serializing structured data.
Fetch polyfill not working with Safari Technology Preview · Issue #303 · JakeChampion/fetch
Using Safari Technology Preview Version 9.1.1 (11601.6.10, 11602.1.25), when I try using fetch: fetch('/') It returns a rejected promise: Promise {status: "rejected", result: &quo...
The 2026-07-28 Specification
The 2026-07-28 Model Context Protocol specification is out, bringing a stateless protocol core, Multi Round-Trip Requests, header-based routing, cacheable list results, authorization hardening, a formal extensions framework, and updated Tier 1 SDKs.

Standard Reader now ships an open AppView for standard.site. Public ATProto queries over the indexed network — publications, articles, feeds, URL resolution. Same lexicons the app uses. Docs + live examples: standard-reader.app/docs/api
API · Standard Reader
standard-reader.appit's easier than ever to turn your standard.site writing into your own website! your posts are atproto records you own. fetch & render them anywhere, in any framework, with your own styles. live demo, try any handle 👇 standard-publication-viewer.wisp.place?handle=erlend.sh
The confusion about standard.site is that there are two distinct and different users. Those that use it as a database schema and those that use it as a new syndication format (like a Wordpress blog with a plugin). But HTML and RSS are views, whereas JSON doubles as both a storage schema and a view
Standard.site - One schema. Every platform.
standard.site