Install Jentic One Beta

Connect the African Market OS MVR API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the African Market OS MVR API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fafricanmarketos.com%2Fafricanmarketos" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fafricanmarketos.com%2Fafricanmarketos" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with African Market OS MVR API.

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

GET STARTED

Start building with African Market OS MVR API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use African Market OS MVR API for, with concrete tasks.

★ 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.

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.

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.

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

26 endpoints — 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.

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

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

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using African Market OS MVR API through Jentic.

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.

African Market OS MVR API

AI ReadinessAI-Aware (B)63/100

See full scorecard

Community OpenAPI document · agent-readyAnalyticsBusiness IntelligenceapiKey26 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For 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.

Use for: Score the relational readiness of a venture entering a new market, Run a relational diagnostic for a stakeholder group, Forecast how a business relationship will develop over the next quarter, Compare the MVR indices of two partner organizations

Not supported: Does not handle payment processing, CRM contact storage, or project management. Use for measuring relational readiness and market-entry trust scores only.

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.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

21%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: BSignals: 4

17%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

93%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: D+Signals: 4

34%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

56%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: B+Signals: 1

70%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the African Market OS MVR API to your agent

Capabilities

Start building with African Market OS MVR API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

African Market OS MVR API

Jentic AI Readiness Score

African Market OS — Minimum Viable Relationships (MVR) API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness