Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the mxverify BV 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%2Fbklink.uk%2Fbklink" | shStep 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%2Fbklink.uk%2Fbklink" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with mxverify BV API.
Look up one site's BV link value by domain with GET /api/v1/bv/{domain}, valuing new sites on demand
Value up to 100 targets in one request with POST /api/v1/bv, getting one result per target in the order sent
Start a bulk valuation job of up to 1,000 targets on a partner key with POST /api/v1/bv/valuations
Poll a bulk valuation job's progress and every site's answer so far with GET /api/v1/bv/valuations/{id}
GET STARTED
Read the link level (A, B, C, or D), caps, model version, and audited flag for each valued site
Show the required 'BV by mxverify' attribution with the report_url returned for each valued or unrated result
Patterns agents use mxverify BV API for, with concrete tasks.
★ Link prospect scoring for an outreach agent through Jentic
A link-building agent that drafts outreach should only pitch sites worth a link. Through Jentic the agent finds the mxverify lookup by intent, sends its prospect list to POST /api/v1/bv in batches of up to 100 targets, and ranks the valued results by the usd figure and level. The mxverify key is injected at call time, so the agent never holds it.
Call POST /api/v1/bv with targets ['example-blog.com','news-site.co.uk','forum.example.org'], then return the targets with status 'valued' sorted by bv.usd descending
Single-site checks before buying or placing a link
Before agreeing a sponsored placement, a marketer wants to know what one followed link from a site is worth. GET /api/v1/bv/{domain} returns the BV figure with its level and caps, such as nofollow lowering the level. A site mxverify has never valued returns valuing with HTTP 202 and retry_after, and a later lookup has the figure.
Call GET /api/v1/bv/example-blog.com; if status is 'valuing', wait retry_after seconds and call it again, then report bv.usd, bv.level, and bv.caps
Bulk valuation of large link lists
Agencies auditing a backlink profile or a prospect database need many sites valued at once. On a partner key, POST /api/v1/bv/valuations starts a job of up to 1,000 targets; sites already valued are answered immediately and new ones are valued as the job reaches them. GET /api/v1/bv/valuations/{id} returns progress and every answer so far, with pending for sites not reached yet.
Call POST /api/v1/bv/valuations with a targets array of 600 domains, store the returned id, then poll GET /api/v1/bv/valuations/{id} until done equals total and summarise the results by level
4 endpoints — the mxverify bv api returns a site's bv, the ranking benefit of one new followed link from that site under mxverify's published model, expressed in us dollars to the cent.
METHOD
PATH
DESCRIPTION
/api/v1/bv/{domain}
Look up one site
/api/v1/bv
Look up many sites
/api/v1/bv/valuations
Start a bulk valuation job
/api/v1/bv/valuations/{id}
Read a bulk valuation job
/api/v1/bv/{domain}
Look up one site
/api/v1/bv
Look up many sites
/api/v1/bv/valuations
Start a bulk valuation job
/api/v1/bv/valuations/{id}
Read a bulk valuation job
What agents get from Jentic-routed access to this vendor.
Setup
Wiring mxverify by hand means handling its key in either the bearer or X-API-Key form, and coding the valuing and retry_after flow for sites it has not valued yet. Through Jentic you install once, import the mxverify BV API from the API Directory, store the key once, and your agent calls it.
Permission scoping
The single-site lookup puts the domain in the URL path, so a rule can pin your agent to one site's lookup, while batch lookups carry targets in the request body and are bounded by operation only. You choose the operations it may call, so paid bulk valuation jobs are not included unless you add them.
Credential isolation
Your mxverify 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 'what is a link from this site worth' or 'value a list of domains', and Jentic returns the matching mxverify operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using mxverify BV API through Jentic.
Is there a mxverify BV MCP server?
You don't need an MCP server to give your agent the mxverify BV API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls it. Operations are discovered on demand, so no extra tool definitions sit in the agent's context.
What authentication does the mxverify BV API use?
Per its OpenAPI spec, the API accepts a key from bklink either as a bearer token in the Authorization header (Authorization: Bearer mxk_...) or as the same key in the X-API-Key header. Through Jentic, the key is stored encrypted by your own Jentic One instance and injected at call time.
What does a BV figure mean?
BV is the ranking benefit of one new followed link from the site under mxverify's published model, given in usd to the cent. It is not a price. Each figure comes with a level (A editorial, B guest or sponsored, C neutralised, D link network), caps explaining what lowered the level, and the model version. Wherever you show a BV, show 'BV by mxverify' linked to the site's report.
Can I limit what my agent is allowed to do with the mxverify BV API?
Yes. Write a rule that allows only GET /api/v1/bv/{domain} and POST /api/v1/bv, so the agent can look up sites but cannot start paid bulk valuation jobs, and every call it makes is logged. You can also pin the single-site lookup to one domain path, such as /api/v1/bv/example.com.
What are the rate limits for the mxverify BV API?
Per the OpenAPI spec, a free key gives 1,000 lookups and 25 new valuations a day, and the partner tier adds volume and bulk valuation jobs paid per call from a bklink wallet. Each target in a multi-site request counts as one lookup, while reading a job is not a lookup. See https://bklink.uk/docs/api for current terms.
How do I value a list of sites through Jentic?
Search Jentic for 'look up the link value of many sites', load the lookupSites operation, and call POST /api/v1/bv with a targets array of up to 100 website addresses. Results come back in the order sent. To run it on your own infrastructure, install Jentic One from its GitHub repo.
For Agents
Look up the BV link value of one site or a batch of sites, start partner bulk valuation jobs, and poll them for results with link level and attribution.
Use for: Get the link value of a site before I pitch a guest post, Check whether a list of 50 prospect domains is worth outreach, I need to value 800 sites from a link-building spreadsheet, Retrieve the progress of my bulk valuation job
Not supported: Does not list a site's backlinks, track keyword rankings, or sell link placements. Use for looking up the BV link value of websites only.
The mxverify BV API returns a site's BV, the ranking benefit of one new followed link from that site under mxverify's published model, expressed in US dollars to the cent. It looks up one site by domain, up to 100 sites in a single request, or up to 1,000 sites in a bulk valuation job for partner keys. Each valued result carries the link level (A editorial, B guest or sponsored, C neutralised, D link network), what capped it, the model version, and an attribution block linking to the site's mxverify report. Sites mxverify has never valued are valued on demand, with the first answer returning a valuing status and a retry_after hint.
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.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>