CitePay lets research agents pay for useful sources, reuse cached access, and keep a clear receipt trail.
Built for feed operators, independent publishers, and AI research products that need a clean way to price, cite, and track source usage. Authors can be registered for direct payouts or marked as claimable until they add payout details.
Research run
Citation budget: $0.20
Grid batteries will likely keep getting cheaper, but project costs will fall less smoothly than cell prices.1
Feed item / cited and paid
Source URL / cited and paid
8
Payees
8
Imported feed items
1
Citation tolls
$0.068
Avg. toll
How it works
CitePay imports source links, maps each source to a payee, and records whether the agent paid, reused cached access, or skipped the source.
Bring in public titles, links, authors, summaries, and categories from feeds or pasted JSON.
Attach a source owner, payout status, price, and cache window.
The agent compares relevance, price, freshness, and budget before paying.
Cited sources create receipts. Cached access avoids repeat payments while it is still fresh.
Where it fits
CitePay does not need a new creator marketplace to start. It works with feeds, source lists, and research-agent workflows that already move links and summaries around.
Infrastructure when you need it
Agent preview
The run makes the spending logic visible: which sources were useful, which were skipped, which were reused from cache, and which created receipts.
Run a question to see sources used, sources skipped, cache reuse, and payment receipts.
Saved to the project ledger.
No agent runs yet.
Source pool
Source records expose enough public context for an agent to decide whether paying is justified.
Feed item
The open source Git project just released Git 2.55. Here is GitHub's look at some of the most interesting features and changes introduced since last time. The post Highlights from Git 2.55 appeared first on The GitHub Blog .
Feed item
Explore how the Open Source Program Office uses GitHub's new license compliance product to manage open source dependencies at scale. The post How GitHub maintains compliance for open source dependencies appeared first on The GitHub Blog .
Feed item
These six free settings will not make your project unhackable. Nothing will. What they will do is close the easy doors. Turn these on, and your project will be meaningfully harder to attack than it was before. The post 6 security settings every GitHub maintainer should enable this week appeared first on The GitHub Blog .
The premise