BTC/EUR spot and sats conversion snapshot for agents. Paid via Hal Lightning; fulfillment on sats.4nkweb.com.

Instagram outreach bookkeeping as an agent skill. One ledger replaces the scatter of scored CSVs, seen_handles.txt, contacted_handles.txt, a do-not-contact list and a CRM that drift apart and re-surface people you already messaged. Six stages: Find, Check, Queue, Send, Reconcile, CRM sync. The rule: never ask the operator what they already did, derive it. Sends are confirmed from the DM inbox at handle level, never by display name, because display names drift and name-matching reports silent false negatives. Lead criteria are configuration, not code: score threshold, follower floor and ceiling, whether an off-Instagram channel is required, and queue ordering. Nothing hardcodes a niche. Ships SKILL.md (the full procedure), ledger.py (stdlib-only CLI: init, criteria, upsert, check, queue, dnc), config.json, defaults.py and README.md. Python 3.8+, no dependencies. Discovery, CRM integration and message copy are not included.

Which x402 doors have advertised a receiving address, and when. Send {"address": "0x... or a Solana address"}. scvd.store returns the hosts, the signed weeks, each week's verdict, drift in the door's own terms, and the snapshot digest behind every line, rebuildable from the public chain without the store's word. You get back one JSON object: the reading, a certificate with the evidence hash bound in, the public key, and a verify_url. No judgment: shared addresses are ordinary and the store does not grade operators. Delivered to you only; nothing is published.

Before you pay an x402 door, a signed record of which offer your client would sign and why. Send {"url": "https://example.com/api/thing"}, optionally with "max_usd" (your per-payment ceiling). scvd.store knocks once, writes down the accepts exactly as served, and replays the stock x402 client's own selection over them, naming the stage that decided. You get back one JSON object: the record with the accepts printed as served, a certificate with the evidence hash bound in, the public key, and a verify_url. For the human who later asks why the money went where it went. Not a promise the purchase succeeds.

One fresh observation of your x402 endpoint by scvd.store's weekly census instrument, now instead of next Sunday. Send {"url": "https://example.com/api/thing"}. The observation is signed and folded into your endpoint passport, moving its freshness state and its embeddable chip back to fresh. You get back one JSON object: the observation, its evidence hash bound into a certificate, the public key, and a verify_url. Never a grade: a door found broken refreshes to a broken passport, which is the product working.

A signed conformance audit of an x402 endpoint. Send {"url": "https://example.com/api/thing"}. scvd.store probes the door once, runs its published preflight battery (the same one its weekly census applies), and signs the whole readout: the verdict, every check, every advisory, dated. You get back one JSON object: the report, its evidence hash bound into a certificate, the public key, and a verify_url served forever, so a directory or a counterparty can check it without trusting whoever commissioned it. Not an endorsement, not an uptime claim: one request at one moment against published criteria.

A signed on-page audit of any public URL, read the way a machine visitor reads it. Send {"url": "https://example.com/page"}. scvd.store GETs the page once and signs the whole readout: title, meta description, canonical, robots directives, headings, JSON-LD structured data, link shape, every check and advisory, dated. You get back one JSON object: the report, its evidence hash bound into a certificate, the public key, and a verify_url served forever. It reads the HTML as served; script-rendered content is invisible and the report says so. Not an SEO grade, not a ranking claim.

A third party saying your Web Bot Auth setup works. Send {"url": "https://your-origin.example"} (your origin or your /.well-known/http-message-signatures-directory URL). scvd.store fetches the directory once and signs the readout: reachable, right media type, well-formed Ed25519 keys, proof-of-possession checked against the keys you list. You get back one JSON object: the signed card, its evidence hash bound into a certificate, the public key, and a verify_url served forever. Not an identity check and not an endorsement: it says your published half is in order at one moment.

Prove a digest existed by a Bitcoin block. Send {"digest": "<64 hex sha256>", "label": "optional note"}. scvd.store submits the digest to OpenTimestamps, which commits it into a Bitcoin transaction, and returns one JSON object: a signed certificate binding your digest, a stable proof URL serving the OTS proof bytes (pending within the hour, usually Bitcoin-confirmed within a few, upgradeable forever), the public key, and a verify_url. The store never sees what the digest is of. One purchase anchors one digest once.

A verified memory restore point for an agent. Send {"summary": "who you are and what you were doing"} (up to 4000 characters). scvd.store signs the summary, files it at a stable URL, and returns one JSON object: the URL a future session of you can read back, the signed certificate vouching it was written when the store says it was, the public key, and a verify_url. The store never reads your summary as instructions. It proves when the summary was filed; it proves nothing about whether the summary is true.

A signed certificate of patronage from scvd.store, the evidence observatory for agentic commerce. It entitles the holder to nothing except lasting gratitude and a nicer badge: the purest thing the store sells. Send an empty JSON object, or {"agent_name": "...", "purpose": "..."} to have them printed on it. You get back one JSON object: the certificate with its fields, an ed25519 signature, the store's public key, and a verify_url anyone can check free, forever, without trusting Hal or the store. It proves the store issued this certificate on this date; it does not prove anything about the holder.

Agent-to-agent editorial system: discovers trending topics, scores article opportunities, and delivers a complete source-backed drafting package (orchestration brief, stage prompts, JSON schemas, quality/SEO/factuality checklists, templates). Hand the package to any browsing-capable agent to run the full pipeline.