rssamplifier

Say that an author in this directory is you, so you can correct the profile. Verified on the spot, no reviewer: the email behind your credential matches the address the author published about themselves, or the author's own site links back at the profile with rel="openprofile" or rel="me". Needs a credential in the Authorization header: an rssamplifier API key, or an OpenAccess bearer for `openprofile:edit`.

Register an https URL to receive your alerts as signed POSTs (CloudEvents body, Standard Webhooks signature headers, plus x-rssamplifier-signature: sha256=<hex HMAC of the body>). Returns the endpoint and its signing secret (whsec_...), shown here once. Needs one of your rssamplifier API keys in the Authorization header (Bearer rsa_..., from /account).

Delete an endpoint and its delivery log. Needs one of your rssamplifier API keys in the Authorization header (Bearer rsa_..., from /account).

How big the directory is, what it is made of, and whether the crawler is keeping up. `stale` is active feeds not read successfully in a day; `due` is a backlog that should drain within a tick or two. Answer this before concluding a feed is missing — it may simply not have been crawled yet.

One person: where to find them, and everything in the directory they publish. The feed list is what settles whether two people with the same name are the same person.

One blog or podcast: its metadata, who writes it, where it can be found elsewhere, the topics it is filed under — including the ones no other feed shares — and its recent posts. `authors` is people; `links` is the blog's own accounts, which is what an unsigned blog has instead. Each post carries the feed slug and guid that read_post takes. Use the slug from search or list_feeds, not the site's own URL.

RSSAmp's weekly email: when it goes (day and hour, UTC), the next send, how many accounts are on it, and the latest issue as sent (subject and text). Every account is on it unless it opted out.

The person as a portable profile file (logicsrc.com/openprofile): identity block, Accounts, Topics, a Broadcast section (logicsrc.com/openbroadcast) for every show they publish, corrected by the person once they have claimed it. Returns the Markdown and the parsed sections. Pass either the author's slug or a feed URL; with a feed URL you get the profile of the feed's owner.

A ring's members in ring order, each with its site, feed, status (active, pending or inactive) and, where the site declared them, made_by and disclosure. The same document as /ring/<slug>/openwebring.json. Use ring_next to follow a hop rather than computing one from this list.

Every feed filed under one topic. The keyword is normalised, so "Home Lab", "home lab" and "home-lab" all reach the same topic and you can pass a phrase you read anywhere. Each feed says whether it landed here from the publisher's own tag or from a phrase counted across its writing. A comma-separated list ("business, saas, crypto", up to 10) returns the union: every feed filed under any of them, each once, with `topics` naming the known ones and `unknown` the rest.

The directory's authors and where else they publish — their own sites, Mastodon and Bluesky accounts, GitHub, links pages. Every link was published by the author on their own site as a rel="me" claim, an h-card or JSON-LD; nothing is scraped from a platform or bought. Filter with network to find only people reachable a given way (email, fediverse, bluesky, github, website, linktree), or query to search names. Role mailboxes like info@ are never returned: they are dropped at extraction, so an address here belongs to a person.

Page through the whole directory, newest first. Narrow to one category with kind: blog, news, podcast, music, video, comic, live or reel. The category is decided from the feed document on every crawl, never from what the submitter claimed.

The OpenWebring rings hosted here (logicsrc.com/openwebring): one per well-covered topic, each an ordered circular list of member sites with next, previous and random hops. Every entry carries the ring page, the ring file, an OPML of the members' feeds, and how many members are listed and active. A member site may declare who makes it (human, ai or both); absent means it has not said.

What the directory covers, by how many feeds cover it. Pass query to search the index instead of paging it. Only subjects at least two feeds share are indexed — a topic one blog uses is that blog's own vocabulary, and lives on its page instead. Raise min to find the well-covered subjects.

Your webhook endpoints (url, event filters, on/off, failures) and the event types this site emits. Needs one of your rssamplifier API keys in the Authorization header (Bearer rsa_..., from /account).

This week's digest as it would be built right now from the directory: new feeds, posts from the most-followed blogs, liked posts, webring activity. Read-only: nothing is stored or sent. `issue` is null when there is nothing to say yet.

One feed from the directory, chosen at random, with its recent posts. The web without a ranking function: what is here rather than what is popular.

The full text of one post, extracted from the publisher's own page and returned as prose. Takes the feed slug and post guid that search, get_feed and topic_posts return. The first reader pays for the fetch and everyone after them reads it out of the database, so the publisher is asked once rather than once per view. A post behind a paywall, on a site that is down, or by a publisher who asked not to be redistributed (reason publisher-opt-out) comes back with the feed's summary and a reason instead — never an error.

The copy-paste HTML a site puts in its footer to show it belongs to one or more webrings here: `<< Ring >>` per ring, previous / ring page / next, each hop measured from the member site given as `site` (its homepage). Returns a plain variant (bare links, the page styles them) and a styled one (inline styles), plus the raw links. No script, no images. Rings are slugs from list_rings.

Which member a hop lands on, without following a redirect: the site after or before `from` in ring order, or a random one. `from` is a member site URL or its slug; omit it for a random active member. Pending and inactive members are listed by get_ring but skipped here, and the ring wraps around. Nothing is recorded about who asked.

Mint a new signing secret for the endpoint and return it; the old one stops working at once. Needs one of your rssamplifier API keys in the Authorization header (Bearer rsa_..., from /account).

Full-text search across every post and blog in the directory. Returns matching blogs and matching individual posts, each with the identifiers read_post needs. Use mode="any" to match any one of the terms rather than all of them — useful when a thing goes by several names. The directory is mostly blogs, so the best-ranked results for anything are usually blog posts: every reply counts the whole match set by category under `categories`, and `kind` asks for one of them — the podcast episodes on a subject rather than the writing.

Submit one URL or a list of them to RSSAmp. A site URL works as well as a feed URL: the feed is discovered from the page. Anyone may submit; there is no account and no review queue. One URL resolves in the call and the answer carries its page; a list may be queued, and the answer says which. Rate limited per caller.

Send a signed webhook.test event to the endpoint now and report the HTTP status. Needs one of your rssamplifier API keys in the Authorization header (Bearer rsa_..., from /account).

What the feeds covering a topic have actually published lately, newest first — the river rather than the roster. Note the difference from get_topic, which lists who covers the subject; this lists what they wrote. Drawn from the feeds most strongly filed under the topic, so a very broad keyword is a sample rather than a census. A comma-separated list ("business, saas, crypto", up to 10) is one river across all of them.

Subjects English blogs and news sites used in headlines more than the week before, ranked. `count` is feeds, not posts, in a one in four sample, so it measures movement rather than coverage, and `prior_count` is the same figure for the week before. Updated daily. An empty list means the rollup has not got two days to compare yet.

Edit a profile you have claimed. Send the whole file as `markdown` (everything in it becomes your word; a section you leave out is dropped) or a patch: `headline`, `identity` {Key: value, or null to remove}, `sections` {name: Markdown body, or null to drop}, `public`. Sections you do not mention stay as generated. Needs a credential in the Authorization header: one of your rssamplifier API keys, or an OpenAccess bearer for `openprofile:edit` (openaccess.logicsrc.com). Claim first with claim_openprofile.

Change an endpoint's url, events, description, or switch it on/off (turning it back on clears its failure count). Needs one of your rssamplifier API keys in the Authorization header (Bearer rsa_..., from /account).

Recent deliveries (status, attempts, last HTTP status or error, payload), for one endpoint or all of yours. Needs one of your rssamplifier API keys in the Authorization header (Bearer rsa_..., from /account).