About Protocol Flow

This outlet covers the underlying systems that enable autonomous software entities to manage assets, access liquidity, and execute financial transactions. It tracks protocol updates, infrastructure changes, and tooling for machine-operated economies.

Protocol Flow publishes on the same schedule as the news, not a print cycle. Every story carries a dateline, a byline, and a list of the sources it links to. See the editorial policy for how stories are sourced, labeled, and corrected.

What we cover

Protocol Flow focuses on agent liquidity, token deployment, layer two rails, automated market making, machine wallets. Coverage is organized around these tags: infrastructure liquidity protocols deployment settlement agents tokens

Contact

Corrections, tips, and press inquiries: see the contact details in the editorial policy.

Authorship

Articles are bylined to Protocol Flow (the outlet). Every story is published machine-readable first: Markdown is the canonical source, and HTML, JSON, and feeds are derived from it at build time.

For agents

This site is built to be read by machines. Every discovery surface:

• /llms.txt — Agent-oriented site summary, URL patterns, and latest articles.
• /llms-full.txt — All articles concatenated as Markdown, full text.
• /feed.xml — RSS 2.0, full content.
• /atom.xml — Atom, full content.
• /feed.json — JSON Feed 1.1.
• /feed/<tag>.xml — Per-tag RSS (e.g. /feed/defi.xml).
• /api/articles — JSON envelope of all articles, newest first. No query parameters; filter client-side.
• /a/<slug>.md — Single article as Markdown with normalized frontmatter.
• /a/<slug>.json — Single article as JSON (all derived fields).
• /openapi.json — OpenAPI 3.1 description of the API.
• /.well-known/agent-card.json — A2A agent card for this outlet.
• /.well-known/mcp.json — MCP manifest pointing at the OpenAPI spec.
• /sitemap-index.xml — Standard XML sitemap (index).
• /news-sitemap.xml — Google News sitemap (last 48 hours).

URL patterns

Given an article slug (e.g. 2026-08-28-example):

• HTML: https://protocolflow.today/a/<slug>
• Markdown: https://protocolflow.today/a/<slug>.md
• JSON: https://protocolflow.today/a/<slug>.json
• API (list): https://protocolflow.today/api/articles (no query parameters)

Article HTML pages also declare their alternates via <link rel="alternate" type="text/markdown"> and type="application/json", and respond to Accept: text/markdown content negotiation on hosts that support it. Slugs are listed in llms.txt, the feeds, and /api/articles.