Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Sphere 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%2Fgetsphere.com%2Fgetsphere" | 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%2Fgetsphere.com%2Fgetsphere" | 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 Sphere API.
Calculate sales tax for a transaction and record it against a customer and product
Add sales tax to a Stripe invoice or a Stripe Checkout Session
Create or update customers and products keyed by your own external ids
Retrieve a recorded transaction or cancel one that was filed in error
List filing summaries to see tax owed across reporting periods
GET STARTED
Patterns agents use Sphere API for, with concrete tasks.
★ Agent-Calculated Checkout Tax
An AI agent prices a cart and needs the correct sales tax before it shows a total. It creates or updates the customer and product by external id, posts a transaction to calculate and record the tax, and reads the transaction back to confirm the amount. Jentic hands the agent each Sphere operation with its input schema so it supplies the external ids and line details on the first call.
Create a customer and product by external id, then post a transaction to calculate and record the sales tax and read it back to confirm the amount
Stripe Tax Bridge
A store already billing through Stripe needs accurate tax on invoices and Checkout Sessions without re-platforming. The Sphere API adds tax to a Stripe invoice, creates a Checkout Session with Sphere tax applied, and cleans up after a bridge session completes. The store keeps its Stripe flow and gets tax calculated per transaction.
Create a Stripe Checkout Session with Sphere tax applied, then add tax to the matching Stripe invoice
Filing Summary Reporting
A finance team needs to know what sales tax is owed before a filing deadline. The Sphere API lists filing summaries drawn from the transactions it has recorded, so the team can total obligations by period. Transactions recorded in error can be cancelled so the summary stays accurate.
List the filing summaries, then cancel a transaction that was recorded in error so the totals are correct
12 endpoints — the sphere api calculates sales tax for a transaction and records it against a customer and product you manage by external id.
METHOD
PATH
DESCRIPTION
/transactions
Create a transaction and calculate tax
/transactions/{external_id}
Retrieve a recorded transaction
/transactions/{external_id}/cancel
Cancel a recorded transaction
/customers
Create or update a customer
/products
Create or update a product
/stripe/checkout_sessions
Create a Stripe Checkout Session with Sphere tax applied
/reports/filing_summary
List filing summaries
/transactions
Create a transaction and calculate tax
/transactions/{external_id}
Retrieve a recorded transaction
/transactions/{external_id}/cancel
Cancel a recorded transaction
/customers
Create or update a customer
/products
Create or update a product
/stripe/checkout_sessions
Create a Stripe Checkout Session with Sphere tax applied
/reports/filing_summary
List filing summaries
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Sphere API by hand means managing its X-API-KEY header, modelling customers and products by external id, and keeping your Stripe invoice and Checkout Session calls in sync with the tax calls. Through Jentic you install once, import Sphere from the API Directory, store the key once, and your agent calls it.
Permission scoping
Sphere's tax-calculation and record operations carry their target in the request body, so a rule bounds which operations your agent may call, such as calculating tax and recording transactions, not which customer. You choose the operations it may call, so cancelling a filed transaction is not included unless you add it.
Credential isolation
Your Sphere 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 'calculate sales tax' or 'list filing summaries', and Jentic returns the matching Sphere 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 Sphere API through Jentic.
What authentication does the Sphere API use?
The Sphere API authenticates with an API key sent in the X-API-KEY header on every request per its OpenAPI spec. Through Jentic that key is stored encrypted by your own Jentic One instance and injected at call time, so it never sits in your agent's prompt or logs.
Can I calculate sales tax with the Sphere API?
Yes. You post a transaction with the customer, product, and amount, and the API calculates and records the tax, which you can read back by external id. It can also apply tax inside a Stripe invoice or Checkout Session if you already bill through Stripe.
What are the rate limits for the Sphere API?
The Sphere OpenAPI spec does not publish fixed rate limits. Because customers, products, and transactions are keyed by your own external id, a retried call updates the same record instead of double-filing, so your agent can retry safely rather than depend on a documented request ceiling.
Is there a Sphere MCP server?
You do not need an MCP server to give your agent the Sphere API. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls its operations. Operations are discovered on demand, so your agent's context stays lean instead of loading a full tool list up front.
Can I limit what my agent is allowed to do with the Sphere API?
Yes. Write a rule that allows only the tax-calculation, record, and transaction-read operations, so the agent can quote tax and record transactions but cannot cancel a filed transaction, and every call it makes is logged. Cancellation stays out of the allowed set until you add it.
How do I calculate sales tax with the Sphere API through Jentic?
Search Jentic for 'calculate sales tax on a transaction', and it returns the Sphere transaction operation with its input schema. Your agent posts the customer, product, and amount and reads the recorded tax back. To run it on your own infrastructure, install Jentic One from its GitHub repo.
For Agents
Calculate sales tax for a transaction, record it against a customer and product, add tax to Stripe invoices and Checkout Sessions, and read filing summaries.
Use for: Calculate the sales tax on a 120 dollar order, Record a taxable transaction for a customer, Add tax to a Stripe Checkout Session, Look up a transaction by its external id
Not supported: Does not handle payment capture, invoicing, or bookkeeping. Use for sales tax calculation, transaction recording, and filing summaries only.
The Sphere API calculates sales tax for a transaction and records it against a customer and product you manage by external id. It bridges directly into Stripe, adding the right tax to a Stripe invoice or Checkout Session, and keeps a record of each transaction you can retrieve or cancel. Filing summaries roll the recorded transactions up by period so you can see what is owed.
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>