canonical: https://jentic.com/apis/africanmarketos.com/africanmarketos # African Market OS MVR API The African Market OS MVR API computes a Minimum Viable Relationships index that measures trust, belonging, permission, and embeddedness to gauge how ready a venture is to enter a high-context market. It runs relational diagnostics, aggregates stakeholder survey feedback into a single score, forecasts how relationship dynamics will shift over time, and benchmarks an entity against sector baselines. It also returns structured insights, narrative stories, and rollout blueprints grounded in the underlying MVR data. The index builds on the published MVR Framework and is aimed at teams making market-entry and partnership decisions. ## For AI agents Compute relationship-readiness scores for market entry: run relational diagnostics, forecast trust dynamics, benchmark against sector baselines, and retrieve structured insights from an entity's MVR data. ## Scope Does not handle payment processing, CRM contact storage, or project management. Use for measuring relational readiness and market-entry trust scores only. ## Capabilities - Compute the Minimum Viable Relationships index from stakeholder trust, belonging, permission, and embeddedness inputs - Run relational diagnostics that pinpoint which trust dimensions are weak for an entity - Forecast how an entity's relationship dynamics will shift over time from historical MVR data - Benchmark an entity's MVR index against sector baselines and compare two entities side by side - Aggregate stakeholder survey feedback into a single MVR index - Generate narrative stories and rollout blueprints grounded in an entity's MVR data ## Use cases ### Agent-driven market-entry readiness check An AI agent assembling a market-entry brief can call the African Market OS API through Jentic to turn stakeholder trust and embeddedness inputs into a Minimum Viable Relationships index, then pull diagnostics and insights to explain the result. Jentic's intent search returns the scoring operation from a natural-language query, so the agent does not need to read the reference docs before its first call. Example prompt: Search Jentic for 'score relationship readiness', load the scoring schema, submit the stakeholder trust and embeddedness inputs for the target venture, and return the computed MVR index with its structured insights. ### Stakeholder trust diagnostics Aggregate survey responses from a stakeholder group into one MVR index, then run a relational diagnostic to see which of the trust, belonging, permission, and embeddedness dimensions is dragging the score down. Teams use this to decide where to invest relationship-building effort before a launch rather than reacting after a deal stalls. Example prompt: Aggregate the stakeholder survey payload into an MVR index, then run a relational diagnostic on the same entity and report which trust dimension scored lowest. ### Sector benchmarking for investment decisions Benchmark a target entity's MVR index against its sector baseline and compare two candidate partners side by side to support an investment or partnership decision. The benchmark and compare operations return the gap to the sector, so an analyst can rank options by relational readiness rather than gut feel. Example prompt: Benchmark the target entity's MVR index against its sector baseline, then compare it with a second candidate entity and return the one with the stronger relational readiness. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/v1/diagnose` | Run a relational diagnostic | | GET | `/v1/scores` | Compute the MVR index | | POST | `/v1/forecast` | Forecast future relationship dynamics | | POST | `/v1/compare` | Compare the MVR indices of two entities | | POST | `/v1/benchmark` | Benchmark an index against sector baselines | | POST | `/v1/insights` | Retrieve structured insights for an entity or sector | | GET | `/v1/trends` | Analyze historical relationship trends | | POST | `/v1/survey-aggregate` | Aggregate stakeholder feedback into an MVR index | ## Key resources - **Scores** — Compute the MVR index and read diagnostic scores for an entity - **Intelligence** — Retrieve insights, forecasts, comparisons, and sector benchmarks - **Context** — Read cultural and relational context and historical relationship trends - **Webhooks** — Register and verify webhook subscriptions for MVR events - **Administration** — Create sessions, validate the license key, and read current usage ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 63 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 80 / 100 - Developer Experience & Jentic Compatibility: 65 / 100 - AI-Readiness & Agent Experience: 48 / 100 - Agent Usability: 94 / 100 - Security: 50 / 100 - AI Discoverability: 70 / 100 - **View full report:** https://jentic.com/apis/africanmarketos.com/africanmarketos/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring the African Market OS MVR API by hand means learning its two API-key headers, the x-mvr-license license key and the x-buyer-email caller header, and coding each scoring and diagnostic call yourself. Through Jentic you install once, import the API from the API Directory, store the license key once, and your agent calls it. - **Permission scoping:** The MVR endpoints carry no resource id in the URL path, so bound your agent to the operations it needs, such as computing a score and reading insights. You choose which operations it may call, so a calibration operation like auto-learn is not included unless you add it. - **Credential handling:** Your African Market OS license key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'score relationship readiness' or 'forecast market trust', and Jentic returns the matching African Market OS operation with its input schema so the agent calls the right endpoint without reading the reference docs. ## Related APIs - **Domo API** — General business-intelligence platform for dashboards and metrics - **Segment Public API** — Customer data pipeline that collects and routes event data - **Count Public API** — Collaborative data analysis and notebook platform ## FAQ ### Is there an African Market OS MVR API MCP server? You do not need an MCP server to give your agent the African Market OS API. Jentic connects it directly from the API Directory: import the API, store your license key once, and your agent calls its scoring, diagnostic, and forecasting endpoints. Operations are discovered on demand, so no extra server definitions load into the agent's context. ### What authentication does the African Market OS MVR API use? The API authenticates with API keys sent in request headers per its OpenAPI spec: a license key in the x-mvr-license header, alongside an x-buyer-email header that identifies the caller. Through Jentic the license key is stored encrypted in your own Jentic One instance and is supplied only when an allowed call runs, so it never reaches the agent's context. ### Can I forecast future relationship dynamics with the African Market OS MVR API? Yes. The forecasting endpoint projects future relationship dynamics from historical MVR data, and the trends endpoint returns the historical series it builds on. Pair them to show where a relationship is heading before committing to a market entry. ### What are the rate limits for the African Market OS MVR API? The OpenAPI spec does not specify rate limits. The spec does expose a usage endpoint that reports current consumption for your license key, and you can confirm current limits in the African Market OS documentation at https://africanmarketos.com. ### Can I limit what my agent is allowed to do with the African Market OS MVR API? Yes. Write a rule that permits only the read and scoring operations, for example computing the MVR index and retrieving insights, so the agent can analyze relationships but cannot trigger the auto-learn calibration operation, and every call it makes is logged. ### How do I compute an MVR score with the African Market OS MVR API through Jentic? Search Jentic for 'score relationship readiness' to surface the scoring operation, load its input schema, pass the stakeholder inputs, and execute. You can install the self-hosted runtime with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`. To run it on your own infrastructure, install Jentic One from its GitHub repo.