{"name":"The Leo King Business Intelligence API Migrations","version":"v1","status":"public-contract","contractVersion":"2026-07-07.enterprise-trust-console-audit-webhook-versioning-limits-examples-support-procurement-conformance-data-processing-launch-readiness-access-control-compliance-map-ai-governance-v1","lastReviewedAt":"2026-07-07","policy":{"status":"live","compatibilitySource":"/api/v1/versioning","breakingChangeNotice":"Breaking changes require a changelog entry, OpenAPI update, migration guide, support path, and the notice window defined in /api/v1/versioning before removal.","legacyAliasPolicy":"Legacy alpha aliases remain available until a dated migration window is published and buyer-path smoke proves the replacement route.","requiredMigrationArtifacts":["Changelog entry with exact affected routes and dates.","OpenAPI diff or replacement schema reference.","Before/after request and response examples.","SDK helper alias or explicit no-alias decision.","Support packet guidance and escalation route.","Post-deploy smoke proof for old and new paths during overlap."],"partnerChecklist":["Pin clients to https://api.theleokingai.com and /v1/* paths.","Read /api/v1/changelog before package or route upgrades.","Preserve Idempotency-Key behavior while changing routes.","Run one core route and one affected paid route in a staging backend before production.","Keep request_id, endpoint, key prefix only, and sanitized payload shape for support."]},"lifecycle":{"currentVersion":"v1","deprecationPolicy":{"minimumNotice":"90 days for beta/public metadata routes; 180 days target for paid production routes once enterprise terms are signed.","announcementSurfaces":["/api/v1/changelog","/api/v1/versioning","/api-docs#changelog","SDK release notes once packages are published","enterprise support packet for signed customers"],"migrationSupport":["OpenAPI examples for old and new fields during the overlap window.","SDK helper aliases where practical.","Buyer-path smoke updates before old behavior is removed."]},"sunsetPolicy":{"minimumNotice":"No paid production route should be sunset without a replacement path, migration window, and support escalation path.","requirementsBeforeSunset":["Replacement endpoint or documented non-replacement rationale.","Changelog entry with exact dates.","OpenAPI update and docs update.","Enterprise account notice when signed terms apply."]},"legacySupport":{"routes":["/api/v1/customer/profile","/api/v1/mundane/forecast"],"policy":"Legacy aliases stay available during alpha migration and must keep response envelopes compatible until the changelog publishes a migration window."}},"guides":[{"id":"legacy-alpha-host-to-dedicated-gateway","title":"Move From Website API Host To Dedicated Gateway","status":"live","audience":"Alpha partners using https://theleokingai.com/api directly.","from":"https://theleokingai.com/api/v1/*","to":"https://api.theleokingai.com/v1/*","reason":"Dedicated gateway routing makes docs, OpenAPI, Postman, SDK defaults, and production smoke align with the public API host.","timeline":"Available now; legacy website host remains backward compatible during alpha.","steps":["Change baseUrl to https://api.theleokingai.com.","Keep the same /v1 route paths and x-api-key header.","Run /v1/status, /v1/openapi, and one core route from a backend environment.","Confirm response envelopes still include request_id, data, usage, and meta."],"validation":["GET https://api.theleokingai.com/v1 returns the API index.","GET https://api.theleokingai.com/openapi.json rewrites to /api/v1/openapi.","Buyer-path smoke proves usage ledger rows for paid routes before production traffic moves."]},{"id":"customer-profile-alias-to-audience-insights","title":"Move Customer Profile Alias To Audience Insights","status":"beta","audience":"Commerce, CRM, funnel, and audience-scoring partners using the early customer profile alias.","from":"POST /v1/customer/profile","to":"POST /v1/audience/insights","reason":"Audience Insights is the business-facing route name for campaign-fit scoring and customer intelligence.","timeline":"No removal date is scheduled. A dated migration window must be published before any alias sunset.","steps":["Keep request payloads grouped under customers and campaign_context.","Switch SDK calls from customer profile aliases to audienceInsights / audience_insights when available.","Compare request_id, usage.lane, credits, and model metadata for equivalent staging calls.","Update support runbooks to reference /v1/audience/insights."],"validation":["OpenAPI documents /v1/audience/insights as the canonical route.","The legacy alias remains listed under /api/v1/versioning until a migration window is published.","Output quality must remain business-grade and fallback-looking responses must fail."]},{"id":"mundane-forecast-alias-to-world-signals","title":"Move Mundane Forecast Alias To World Signals","status":"beta","audience":"BTV, media, market, geopolitical, research, and forecast partners.","from":"POST /v1/mundane/forecast","to":"POST /v1/world/signals or POST /v1/world/signals/jobs","reason":"World Signals is the commercial product lane for BTV-style intelligence, with async jobs for deeper production forecasts.","timeline":"No removal date is scheduled. Async job adoption is recommended before high-volume deep forecast use.","steps":["Use /v1/world/signals for synchronous forecasts and /v1/world/signals/jobs for deep async work.","Store job_id and status_url when using async jobs.","Poll until complete or failed; do not bill polling as usage.","Review quality metadata and BTV evidence before publishing output to users."],"validation":["Async create returns 202 with status_url and reserved credits.","Completed jobs include data.result, usage, and meta.","Quality gates reject generic, incomplete, or fallback-looking forecasts before billing."]}],"links":{"docs":"/api-docs","openapi":"/api/v1/openapi","versioning":"/api/v1/versioning","accessControl":"/api/v1/access-control","changelog":"/api/v1/changelog","examples":"/api/v1/examples","sdks":"/api/v1/sdks","support":"/api/v1/support","procurement":"/api/v1/procurement","conformance":"/api/v1/conformance","dataProcessing":"/api/v1/data-processing","compliance":"/api/v1/compliance","errors":"/api/v1/errors"}}