Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Orizn Visa 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%2Forizn.app%2Forizn" | 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%2Forizn.app%2Forizn" | 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 Orizn Visa API.
Look up full visa requirements for a passport and destination pair
Run a lightweight yes/no visa check for a pair
Fetch all destinations for a single passport in bulk
Resolve a multi-passport group trip to a shared outcome
Compute a passport mobility score and compare two passports
GET STARTED
Make an itinerary decision across a whole trip rather than one pair
Patterns agents use Orizn Visa API for, with concrete tasks.
★ AI Agent Visa Check
An AI agent connected through Jentic answers travel questions by checking whether a given passport needs a visa for a destination and returning the requirement with fees and transit rules. The lightweight check gives a fast yes/no, while the full lookup returns the complete set of data points for a confident answer.
Check whether a US passport needs a visa for Japan and return the requirement and fees
Trip Planning Across Destinations
A travel planner's agent fetches all destinations a passport can enter in a single bulk call and sorts them by whether a visa is required. This supports 'where can I go visa-free' style planning without one call per country.
Fetch all destinations a given passport can enter and group them by requirement
Passport Mobility Comparison
To compare travel freedom, an agent computes mobility scores for two passports and returns the comparison. The score and compare operations summarize how many destinations each passport reaches, which is useful for relocation or dual-citizenship decisions.
Compute mobility scores for two passports and compare them
30 endpoints — the orizn visa api returns visa requirements, fees, embassy details, transit rules, and more for passport and destination pairs, with up to 30 data points per pair in 15 languages.
METHOD
PATH
DESCRIPTION
/api/v1/visa
Full visa intelligence for a pair
/api/v1/visa/check
Lightweight yes/no visa check
/api/v1/visa/bulk
All destinations for a passport
/api/v1/visa/group
Multi-passport group trip
/api/v1/visa/score
Passport mobility score
/api/v1/visa/score/compare
Compare two passports
/api/v1/visa/decision
Itinerary decision for a trip
/api/v1/visa
Full visa intelligence for a pair
/api/v1/visa/check
Lightweight yes/no visa check
/api/v1/visa/bulk
All destinations for a passport
/api/v1/visa/group
Multi-passport group trip
/api/v1/visa/score
Passport mobility score
/api/v1/visa/score/compare
Compare two passports
/api/v1/visa/decision
Itinerary decision for a trip
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Orizn Visa API by hand means managing its API key in the `x-api-key` header or `api_key` query parameter, separating public endpoints from key-gated ones, and shaping each passport and destination query yourself. Through Jentic you install once, import Orizn from the API Directory, store the key once, and your agent calls it.
Permission scoping
The Orizn Visa API carries the passport and destination in query parameters, so rules bound which operations your agent may call, not which countries it queries. You choose the operations it may use, such as visa lookups and checks, so creating webhooks or managing team keys is not included unless you add them.
Credential isolation
Your Orizn API 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 'check visa requirements' or 'compare two passports', and Jentic returns the matching Orizn operation with its input schema so the agent calls the right endpoint without reading the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Orizn Visa API through Jentic.
What authentication does the Orizn Visa API use?
The data endpoints authenticate with an API key, passed in the `x-api-key` header or as an `api_key` query parameter, as declared in its OpenAPI spec. Many endpoints such as stats, scores, and live activity are public and need no key, and dashboard-only operations use the `orizn_token` session cookie. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time.
Can I check whether a passport needs a visa with the Orizn Visa API?
Yes. The check operation returns a lightweight yes/no result for a passport and destination, while the full visa operation returns the complete set of data points including fees, embassy details, and transit rules.
What are the rate limits for the Orizn Visa API?
The OpenAPI spec does not publish fixed rate limits; several endpoints count against your monthly plan allowance. See the Orizn documentation at https://visa.orizn.app for the limits that apply to your plan.
Can I limit what my agent is allowed to do with the Orizn Visa API?
Yes. Write a rule that allows only the visa-lookup and check operations, so the agent can read visa requirements but cannot create webhooks, manage team keys, or rotate your API key, and every call it makes is logged.
How do I check visa requirements with the Orizn Visa API through Jentic?
Search Jentic for 'check visa requirements', add the Orizn Visa API from the directory, and store your API key once. Your agent then runs a check or a full lookup for a passport and destination. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Is there an Orizn Visa API MCP server?
You don't need an MCP server to give your agent the Orizn Visa API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls the visa, check, bulk, and score operations. That keeps extra tool definitions out of the agent's context.
For Agents
Look up visa requirements, fees, and transit rules for passport and destination pairs, run yes/no checks and bulk lookups, and compute passport mobility scores.
Use for: Check whether this passport needs a visa for a destination, Look up the full visa requirements for a passport and country, Get all destinations a passport can enter, Compare the mobility of two passports
Not supported: Does not handle flight booking, hotel reservations, or passport applications. Use for visa requirement data and passport scoring only.
The Orizn Visa API returns visa requirements, fees, embassy details, transit rules, and more for passport and destination pairs, with up to 30 data points per pair in 15 languages. It answers single-pair lookups and lightweight yes/no checks, bulk lookups for a whole passport, multi-passport group trips, and itinerary decisions, and it computes passport mobility scores and comparisons. Device, webhook, and team-key operations manage subscriptions and access for higher tiers.
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>