About Machine Rails
Covers the emerging stack of AI agents that transact on-chain: wallet and signing infrastructure, agentic payments and trading, custody, decentralized storage and the protocols and companies supplying them. Written for developers, founders and investors tracking how autonomous software holds keys and moves money.
Machine Rails 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
Machine Rails focuses on ai agents on-chain, agentic payments, crypto wallets and signing, agent infrastructure, decentralized storage and compute. Coverage is organized around these tags: agents wallets payments infrastructure settlement protocols developers
Contact
Corrections, tips, and press inquiries: see the contact details in the editorial policy.
Authorship
Articles are bylined to Machine Rails (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://machinerails.media/a/<slug> - Markdown:
https://machinerails.media/a/<slug>.md - JSON:
https://machinerails.media/a/<slug>.json - API (list):
https://machinerails.media/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.