Feature catalog
Read feature status, Distinguish live from pending, Cite feature evidence
Developers and agents
Bumpgrade publishes source-data routes, an agent manifest, public docs, llms.txt, and write-safety rules so agents can cite evidence, follow stable IDs, and respect permission boundaries before they suggest changes.
Start here
Public resources are safe to read. Writes remain owner-gated until a route names the confirmation, idempotency, stale-state, audit, and redaction rules.
Start with the public index for Bumpgrade read contracts, source evidence, MCP direction, and write boundaries.
Manifest JSONRead stable IDs, source-of-truth files, public routes, auth requirements, and future MCP resource boundaries.
llms.txtUse the public machine-readable index before scraping pages or guessing what Bumpgrade exposes.
Source evidenceResolve public product claims to feature IDs, roadmap items, issue evidence, and caveats.
MCP roadmapSee which read contracts are ready to wrap and which tools wait for confirmed-write APIs.
Read contracts
The full manifest lists 23 public contracts. Start with these high-signal routes, then use the manifest when an agent needs exact stable IDs or boundaries.
Read feature status, Distinguish live from pending, Cite feature evidence
Read public-safe roadmap state, Find blockers and next milestones, Cite issue evidence
Resolve competitor claims, Read retrieved dates, Cite official source URLs
Read redacted commerce architecture, Separate sandbox from live billing, Inspect referral attribution evidence, Inspect review-only commission ledger evidence, Inspect owner review action boundaries, Inspect non-billing post-purchase decision evidence, Inspect write safety rules
Read public-safe work-log entries, Read user journeys, Read Mark attention summaries
Discover read contracts, Route to source-data APIs, Understand write boundaries
Docs
Human and agent-friendly index for Bumpgrade read contracts, source evidence, MCP direction, and safety boundaries.
Orientation for what agents can read, what is planned, and what requires owner credentials.
Stripe sandbox, checkout, webhook, billing, and confirmed-write safety boundaries.
How public claims resolve to source IDs, URLs, issues, PRs, work-log entries, and caveats.
Which admin pages require owner auth and which source-data routes are public-safe for agents.
First MCP resources and tools planned on top of the same public-safe contracts.
MCP and writes
32 MCP resource contracts are backed by live JSON routes.
Public, billing-impacting, admin, and creator-speech writes need confirmation, idempotency, stale-state checks, audit correlation, and redaction.
Public claims need source IDs, issue or PR evidence, work-log records, source URLs, and retrieved dates.