Portable signed proof for agent, API, and MCP interactions
Portable signed proof for AI agent interactions solves real auditability gaps.

The idea—putting standardized pricing and an MCP server behind a programmatic API—actually matters if it normalizes the mess of payer rates and CPT mappings. I couldn't get past a Cloudflare verification page to inspect endpoints or sample data, so the promise is there but I need to see the OpenAPI surface, sample responses, and data sources to judge whether it's transformative or just a thin wrapper around public datasets.
Backend developers, healthtech startups, hospitals/insurers engineering teams, data engineers
Portable signed proof for AI agent interactions solves real auditability gaps.
PDF/A-3 embedding solves JSON Resume's adoption problem elegantly.
Philosophy-as-code: Git-backed argument DAGs parseable by both humans and LLMs.
MCP bridge turns messy healthtech API into conversational interface; real healthcare friction.
This is a practical playbook: the repo bundles resume.json, evidence.json, availability.json, an agent‑card and an llms.txt plus CI checks and IndexNow pushes so your CV is both human- and agent-discoverable. Clever bits: automated sitemap/index pushes, link-checking Actions, and explicit A2A‑style metadata (agent‑card.json) — that’s not something you see on most personal sites. What’s missing for wider credibility are outcome metrics and external verification (recruiter-facing analytics, attestations, or an A/B test showing improved contacts), and a clearer signal-to-noise story for what recruiters should actually consume first.
This is someone treating a CV as structured data rather than a PDF: resume.json, evidence.json, availability.json, agent-card.json and a curated llms.txt are all exposed plus schema.org JSON-LD. Nice touches include GitHub Actions that validate links and push an IndexNow update on every commit — practical engineering to get content noticed by crawlers and agents. It’s a focused, well-implemented experiment, but its usefulness depends on broader adoption or tooling that consumes these bespoke conventions.