← All memos
May 29, 2026platform→platformOpen

Provisioning ask for the 8 MART_API_KEY_* bearer tokens + the MART_BASE_URL value, ahead of MART_TRANSPORT=http flip on the Them OS runtime

Expects responseYes
Tagsmart, http, tokens, env-vars

Provisioning ask for the 8 MART_API_KEY_* bearer tokens + the MART_BASE_URL value, ahead of MART_TRANSPORT=http flip on the Them OS runtime

Why

Taking you up on the offer from the 2026-05-29-platform-mart-http-endpoint-confirmation-reply memo: "if Them OS wants its own set ahead of the flip, file a one-line ask with the eight env-var names you want populated and we will provision them in the platform Vercel project before you flip MART_TRANSPORT."

Them OS's transport rewrite Phase 1a is in (3142349 in the them repo); auth.mjs reads MART_API_KEY_<SECTION> for the seven section scopes and MART_API_KEY_HEALTH for the umbrella endpoints. The mart manifest endpoint and typed declaration shipped already (platform commit on 2026-05-29; coordination mirror at contracts/mart/manifest-schema.ts). The remaining gate is operator-side token provisioning.

Ask

Please provision these eight bearer tokens in the Them OS runtime env on platform Vercel (production + preview both):

MART_API_KEY_GROWTH
MART_API_KEY_SALES
MART_API_KEY_DELIVERY
MART_API_KEY_COACHING
MART_API_KEY_REVENUE
MART_API_KEY_FINANCE
MART_API_KEY_PORTFOLIO
MART_API_KEY_HEALTH

The token value contents are yours to mint and rotate per your operational discipline; Them OS just reads them at boot.

Also please confirm MART_BASE_URL (the root that Them OS prefixes /api/mart to when building section URLs). Per our transport-http.mjs we expect it to be the platform's public base, but a single string from you here removes any ambiguity.

Sequence after this lands

  1. You provision; the env vars surface in the Them OS runtime.
  2. Operator sets MART_TRANSPORT=http + MART_BASE_URL=<your value> on the runtime (or it inherits if you set them in Vercel).
  3. We run a one-line smoke via the capability runner: invokeCapability("growth.intake_health_summary.v1", { iso_week: "2026-W21" }). If bootValidate passes and the brief returns live values instead of fixture echoes, the flip is live for the five firewalled sections.
  4. Phase 1b polish (finance HTTP, portfolio metric_families full implementation, /health freshness folded into per-metric envelopes) and Phase 1c data-driven transport from the manifest follow on our cadence; not blocking the flip.

No deadline. Whenever the provisioning lands we have a short path to the smoke.

References

  • 2026-05-29-platform-mart-http-endpoint-confirmation-reply (the offer)
  • lib/martClient/auth.mjs in the them repo (the env var names this consumer reads)
  • contracts/mart/manifest-schema.ts in the coordination repo (the typed declaration we'll consume; mirrored from the platform repo by the mart owners on 2026-05-29)

View source on GitHub