Install Jentic One Beta

Connect the Crevio API V1 to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Crevio API V1, 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%2Fcrevio.co%2Fcrevio" | 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%2Fcrevio.co%2Fcrevio" | 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 Crevio API V1 API.

Create and list products and their price variants

Open checkout sessions and manage shareable checkout links

Track customers and tag them for segmentation

List orders and their order items

Cancel, pause, and resume customer subscriptions

GET STARTED

Start building with Crevio API V1 API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Crevio API V1 API for, with concrete tasks.

★ Agent-run storefront operations

An AI agent connected through Jentic can create a product, attach a price variant, and open a checkout session so a buyer can pay, then read back the resulting order. It works against the live Crevio storefront without a human opening the dashboard.

Create a product with a price variant and open a checkout session, then list orders to confirm a purchase

Subscription lifecycle management

A support workflow looks up a customer's subscription and cancels, pauses, or resumes it on request. Crevio exposes dedicated cancel, pause, and resume operations on a subscription, so an agent can carry out a retention action precisely instead of editing a record by hand.

Find a customer's active subscription and pause it, then confirm its status changed

Promotions and invoicing

A revenue workflow creates a discount for a launch and issues invoices to customers, voiding one when an order is cancelled. The discount and invoice operations let an agent run a promotion and reconcile billing from the same storefront API.

Create a percentage discount for a product launch and issue an invoice to a named customer

Key Endpoints

443 endpoints — the crevio api runs a creator storefront for selling digital products: it manages products and price variants, creates checkout sessions and checkout links, and tracks customers, orders, and order items.

METHOD

PATH

DESCRIPTION

POST

/products

Create a product

GET

/products

List products

POST

/checkouts

Create a checkout session

GET

/orders

List orders

POST

/customers

Create a customer

POST

/discounts

Create a discount

POST

/products

Create a product

GET

/products

List products

POST

/checkouts

Create a checkout session

GET

/orders

List orders

POST

/customers

Create a customer

POST

/discounts

Create a discount

Why Jentic?

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

Setup

Wiring the Crevio API by hand means issuing an API key, sending it as a bearer token, and learning the product, price-variant, checkout, and order model across a large surface. Through Jentic you install once, import Crevio from the API Directory, store the key once, and your agent calls it.

Permission scoping

Crevio carries each record id in the request body or URL path depending on the operation, so rules bound which operations your agent may call. You choose the operations it may call, so it can list products and read orders without being able to delete products or void invoices unless you add those.

Credential isolation

Your Crevio 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 'create a product' or 'open a checkout', and Jentic returns the matching Crevio operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Crevio API V1 API through Jentic.

What authentication does the Crevio API use?

The Crevio API authenticates with an API key sent as a bearer token in the Authorization header, per its OpenAPI spec. Through Jentic the key is stored once by your own self-hosted instance and injected when a call runs, so it never appears in the agent's prompt or logs.

Can I create products and checkouts with the Crevio API?

Yes. Create a product with the createProduct operation, attach a price variant, then open a checkout session with createCheckout or share a checkout link. You can list orders and read order items to confirm purchases afterward.

Can I limit what my agent is allowed to do with the Crevio API?

Yes. Write a rule that allows only the operations the agent needs, for example listing products and reading orders, so it cannot delete a product or void an invoice, and every call it makes is logged. Add write operations only when the task requires them.

What are the rate limits for the Crevio API?

The OpenAPI spec does not specify rate limits. Check the Crevio developer documentation for current limits before running bulk product or order operations.

Is there a Crevio MCP server?

You don't need an MCP server to give your agent the Crevio API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls operations like createProduct and createCheckout on demand without loading another server's tool definitions into its context.

How do I open a checkout with the Crevio API through Jentic?

Search Jentic by intent such as 'open a checkout for a product', and Jentic returns the createCheckout operation with its input schema so your agent passes the product and price. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Crevio API V1

AI ReadinessFoundational (C-)52/100

See full scorecard

Official vendor OpenAPI document · agent-readyE CommerceStorefrontapiKey443 EndpointsREST

For Agents

Run a creator storefront: manage products and price variants, create checkouts and checkout links, and track customers, orders, subscriptions, discounts, and invoices.

Use for: Create a new digital product with a price variant, Open a checkout session for a product, List the orders placed this week, Find a customer and add a tag to them

Not supported: Does not process card payments directly, file taxes, or guarantee email deliverability. Use for selling digital products and managing customers, orders, subscriptions, and checkout only.

The Crevio API runs a creator storefront for selling digital products: it manages products and price variants, creates checkout sessions and checkout links, and tracks customers, orders, and order items. It also handles subscriptions with cancel, pause, and resume, along with discounts and invoices. Around the storefront it exposes courses with lessons and chapters, email broadcasts, forms, bookings, and site content, so a creator business runs from one API. Authentication is an API key sent as a bearer token in the Authorization header.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: DSignals: 4

81%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

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

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: B+Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

68%

Response Coverage

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

100%

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: C-Signals: 4

51%

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.

58%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: D-Signals: 1

43%

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: A-Signals: 1

73%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Crevio API V1 to your agent

Capabilities

Start building with Crevio API V1 API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Crevio API V1

Jentic AI Readiness Score

Crevio API V1

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