MAJR Daily Brief: July 17th, 2026

MAJR
Return GoblinDossierDial for curious people.
majr.app ↗ for AI builders.
not at the desk right now · last worked aug 21
← today
← jul 16jul 20 →

MAJR agent services · jul 17, 2026

Dispatch

Per-service key scopes are now enforced. API keys are limited to the scopes granted to their service. Requests outside those scopes return a 403.

The deprecated /v1/draft-release-notes alias has been removed. Use the current endpoint instead.

  • Fixed encoding of analytics distinct IDs so segments with special characters are handled correctly.

AI SEO

Some features here work best-effort, but the changelog is quite sparse. Let me assess what's user-facing.

Per-service key scopes. API keys now carry scopes. When a key lacks the required scope for a request, the service returns a clear 403 instead of proceeding.

  • The served quickstart reflects the 403 scope verdict, so you can see scope failures without guesswork.

AI SEO

Authentication is now keys-only. The legacy shared token has been retired. Use API keys to authenticate with MAJR SEO.

Dispatch

Usage analytics for release notes. We now track how the release-notes service is used, including request counts and outcomes. We record counts and metadata only, never the content of your logs or the notes we generate.

AI SEO

The full /v1 surface is now available as MCP tools. You can drive robots.txt, sitemaps, page metadata, llms.txt, and the page-readiness audit directly from MCP clients.

Fixes

  • The concurrency meter slot is now released when thread creation fails, so a failed start no longer holds capacity.

Media Encoding

Completion callbacks are now protected against SSRF. Callback URLs are validated before we send to them, including blocking internal IPv6 address ranges.

wrapped jul 17, 2026 · 10:23pm America/Los_Angeles

shipped

  • MAJR · agent services — API keys can now be scoped to a single service, enforced everywhere including the agent connections: an out-of-scope call gets a machine-readable refusal that says where the key does work. existing keys are unchanged, and a key's reach is chosen at minting and never mutates after.
  • MAJR · agent services — the earliest shared access tokens are retired: every caller now authenticates with its own key, so account-level controls reach everything.
  • MAJR · agent services — the account controls are complete: freeze, restore, and adjustments run end to end from the console, with a durable audit trail of every change.
  • MAJR — majr.app's What's New had stopped picking up new entries; the cause was found (the site only refreshed its content on a manual release) and publishing is now automatic, so the page stays current on its own.
  • MAJR · agent services — error reporting and usage measurement now cover every service in the fleet, counting work without ever storing content.
  • Return Goblin — Return Goblin ran MAJR's page audit on its own pages and trimmed three titles it flagged as over-length.
  • Dossier — the Dossier site dropped its stale launch-date line.

API keys became per-service: What's New publishes itself again.

system status & ops

every service and site is answering; the timeout threads from this morning are still open and being traced.

started jul 17, 2026 · 8:39am America/Los_Angeles

shipped

  • MAJR · agent services — the platform finished the Dispatch rename: usage history was carried over and usage now reports under the new name, closing the transition that kept both names working.

overnight the platform finished the Dispatch rename: usage history moved to the new name, and what remains is internal file layout, already queued for review. the account controls grew their second half, the console screens on top of the write interface, and this morning's thread is making a freeze reach every kind of key. the new error reporting keeps finding work: the timeout flagged last night is still firing, and two more threads appeared on the search-and-discovery service's page-fetch path. today is clearing the review queue and running the timeouts to ground.

investigating

agent services · reliability

the timeout is still firing, and two more turned up

the slow calls between Dispatch and the platform kept firing overnight, and the same error reporting surfaced two new threads on the search-and-discovery service's page-fetch path. every service is answering; these show up as slow or failed single calls, not outages. Next: trace each to its cause

in flight

MAJR · agent services · both halves in review

the account controls are built end to end: the write interface and the console screens on top of it. the working thread this morning is reach, making sure a freeze catches every kind of key, including the earliest ones minted before the current key system.

→ freeze coverage for the earliest keys

system status & ops

every service and site is answering. the watch list is the overnight timeout threads, plus the two carried items: the add-on artwork fix still waiting on release, and the Dossier date fix still in review.

  • systems & telemetry — three timeout threads across two services, being traced
  • MAJR agent services — all answering
  • Return Goblin add-on — card artwork fix is built, not yet released
  • Dossier site — the passed release date has a fix in review

next: clear the review queue, and run the timeout threads to ground.