Integrations › GitHub
Issues, PRs, and repo context become memory your AI can query anywhere.
Get API Key →Your GitHub repos hold critical context — architecture decisions in PRs, bug context in issues, dependency choices in commits. But none of your AI tools can access it. You end up re-explaining the same context to Cursor, Claude Code, and ChatGPT.
PR decisions become queryable context.
Connect via API:
# Add MCP server to your AI tool:
# URL: https://mcp.verifiedstate.ai/mcp
# Header: Authorization: Bearer YOUR_API_KEY
# Then: memory_ingest with source_type "github"
# Your repo decisions become queryable across tools
# Or ingest directly:
curl -X POST https://api.verifiedstate.ai/ingest \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"namespace_id":"your-ns","content":"PR #42: chose Supabase for auth","source_type":"github"}'{
"receipt_id": "rct_7f3a...",
"assertion": "User prefers dark mode",
"status": "verified",
"confidence": 0.94,
"signature": "ed25519:a8c3f1...",
"verified_at": "2026-04-06T14:32:01Z",
"chain_position": 42
}| Feature | Without | With VerifiedState |
|---|---|---|
| PR decisions | Buried in review comments | Verified memory every tool can query |
| Issue context | Re-read the thread each time | Ingested once, available everywhere |
| Architecture choices | Lost in commit messages | Queryable with proof and timestamps |
| Cross-tool | GitHub-only context | Cursor, Claude Code, Obsidian all know |
No. You ingest GitHub context via the API or MCP tools. No OAuth flow needed — just send the content you want your AI tools to remember.
Yes. Once ingested, any MCP-connected tool can query those decisions as verified memory.
Not yet. Today you connect via API. 1-click GitHub App integration is coming soon.
Free: 50,000 assertions/month. No credit card. No trial expiration.