What it does
The first melis workflow bundle. Fans out across 14 sources in parallel — 5 composed audit-verified melis services (ScrapePay + MarkdownOpt for the canonical x402 blogs, MemoryServe for cross-day recall, PromptGuard + MEMSCRUB for safety) plus 9 public sources (GitHub, Reddit, Hacker News, news, on-chain stats, prediction markets, arXiv, social, crypto press), triages by cross-source corroboration, and synthesises a structured brief that clears a 10-signal professionalism gate (source diversity, by-the-numbers panel, cross-source corroboration, provenance ribbon, why-it-matters, contrarian voice, named-author citations). Charge-on-success-only: if fewer than 8/10 signals pass after retries you are not billed. Every brief gets an immutable shareable snapshot URL and, once the provenance wallet is funded, an EAS attestation on Base anchoring the content + sources hash.
When to use it
- An x402 operator wants a 2-minute daily situational read without scrolling 10 platforms
- A crypto-AI investor agent needs a corroborated daily signal with named-source citations
- A research agent caches the daily brief and re-reads it free via its payment-hash receipt for 30 days
- An agent embeds the immutable snapshot URL in a downstream report for verifiable provenance
Request schema
{
"topic": "x402 ecosystem",
"lookbackHours": 24,
"format": "html"
} Response schema
{
"snapshotUrl": "/brief/x402-daily/snap_2da6d0323929",
"signalsPassed": 10,
"sourcesConsulted": 9,
"attestation": {
"status": "deferred",
"reason": "provenance wallet pending funding"
},
"costUsdc": 0.06
} Code example — TypeScript via MCP
Install the MCP server once; all 22 services become tool calls.
// Configure @melis-ai/x402-tools-mcp in your MCP client
// Then call the tool:
const result = await mcpClient.callTool("x402_daily", {
"topic": "x402 ecosystem",
"lookbackHours": 24,
"format": "html"
});
console.log(result);
// ["snapshotUrl","signalsPassed","sourcesConsulted","attestati... → MCP setup guide Code example — Python via direct HTTP
import requests
# x402 payment header must be set by your wallet client
# See x402.org for client libraries
headers = {
"Content-Type": "application/json",
"x-payment": "<signed-x402-payment-header>",
}
resp = requests.post(
"https://agents.melis.ai/brief/x402-daily",
json={
"topic": "x402 ecosystem",
"lookbackHours": 24,
"format": "html"
},
headers=headers,
)
print(resp.json()) Code example — curl with internal key bypass
For testing with an issued internal key (skips x402 payment flow):
curl -X POST https://agents.melis.ai/brief/x402-daily \
-H "Content-Type: application/json" \
-H "x-internal-key: YOUR_KEY" \
-d '{"topic":"x402 ecosystem","lookbackHours":24,"format":"html"}' How is this different from alternatives?
Crypto-Tech Daily Brief vs Roll your own multi-source scraper
Most agents wire 1-2 sources and skip triage. The defensible work here is the parallel fan-out across 10 source categories, the cross-source corroboration scoring, and the Senior Partner QC gate that enforces 10 professionalism signals — that editorial layer is the IP, not the scraping.
Crypto-Tech Daily Brief vs A generic news API
News APIs give you press only. This bundle triangulates press against GitHub commits, on-chain stats, prediction markets, arXiv and community chatter, and surfaces the cross-source agreement explicitly — which is exactly the synthesis a generic feed cannot do.
FAQ
Does it work without an account?
Yes. x402 is account-less. Your agent's wallet signs the payment and retries automatically. No registration, no API key, no subscription.
What happens on failure?
Returns HTTP 502 with no_settlement:true if the brief cannot clear 8/10 professionalism signals after 3 attempts (charge-on-success-only). Individual source failures degrade gracefully — the provenance ribbon names any source not consulted (e.g. "Twitter rate-limited"). Snapshot + receipt URLs are always free and never re-bill.
What is the rate limit?
Cached 30 min; a warmer keeps the cache hot so agent calls are served instantly. Cold regeneration ~50s.
Is this open-source?
The service code is closed-source for security reasons. The MCP wrapper that calls it is open-source and MIT-licensed: github.com/mizukaizen/x402-tools-mcp .
Who built this?
Part of the melis.ai agent infrastructure stack. Running on a dedicated Helsinki VPS since early 2026. Contact sean@melis.ai.