Fleet catalog now available at /catalog.json. Query the catalog to see the available agent surfaces programmatically.

• Documented the SEO agent surface and full fleet catalog in the CATALOG file and READMEs.

Agent-ready SEO surface. MAJR SEO now publishes a machine-readable service card and an llms.txt so agents can discover what the service does and how to use it.

• Polished OpenAPI spec makes the API easier to read and integrate against.
• Structured errors follow the problem+json format, so failures come back in a consistent, parseable shape.

Bring your own API keys. You can now add and manage API keys under your account, organized by product. Set which keys are active so each product uses the credentials you intend.

Consistent, quality voice out of the box. Release notes are now composed against a shared voice floor on the server — the same honest, plain-spoken foundation applies no matter which product you're using.

We've also updated the documentation to match.

Use MAJR Release Notes with your AI agents. There's now an MCP endpoint at /mcp (streamable HTTP) that uses the same API keys you already have, so agents can generate release notes without a separate setup.

Discover the API more easily. We've polished the OpenAPI spec and added discovery endpoints at / and /llms.txt, making it simpler for both people and agents to find their way around.

See your usage. A new GET /v1/usage endpoint lets you check your usage directly.

Accounts and authentication. Tenants are now backed by Postgres, with support for two authentication methods.

We've also expanded the agent documentation and runbook to help you get started.

Better crash tracking. We've added optional error reporting so encoding problems get caught and diagnosed faster, on both the server and worker side.

Faster starts for encodes. The encoding API now stays warm and ready, so your jobs kick off without waiting on a cold start.

Wider audio format support. AAC uploads sent as audio/x-aac are now recognized and encoded.

More reliable duplicate handling. When you re-submit a job that's already in progress, we now report its real, current status instead of a stale one.

Internationalized domains now work correctly. URLs with non-ASCII hostnames are handled using IDNA2008 encoding, and any authentication details in a URL are preserved as you entered them.

More reliable audits. The page-readiness audit now handles DNS failover gracefully and won't reuse connections across hosts, so results reflect the site you actually asked about.

Honest audit results. We tightened the audit so it reports what it genuinely found — no overstated pass/fail claims.

Safer fetching by default. The audit and other outbound fetches use a default-deny guard that blocks requests to internal and private addresses, including embedded-IPv4 and NAT64 edge cases. This is a best-effort protection against server-side request forgery.

Cleaner llms.txt and robots handling. llms.txt output is sanitized, and robots handling is hardened against injection.

Turn your development log into release notes. MAJR Release Notes is our first shared service capability — point it at a raw development log and get back concise, customer-facing notes.

• Choose how notes are delivered. A new render target lets you pick the output format that fits your workflow.
• Pick your model. Draft with any model from the supported allowlist.
• Clearer errors. When something goes wrong, the service now returns structured, standards-based error responses (problem+json) so failures are easier to diagnose.