Install Jentic One Beta

Connect the Graunt API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Graunt 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%2Fgraunt.com%2Fgraunt" | 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%2Fgraunt.com%2Fgraunt" | 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 Graunt API.

Search and read public listings of agent-ready data packets

Purchase a listing and receive an entitlement to its packet

Download an entitled packet as a signed-URL list, source archive, or machine ZIP

Mint and revoke scoped access passes and packet access keys for a purchase

Publish a listing as a seller through a packet upload session

GET STARTED

Start building with Graunt API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Graunt API for, with concrete tasks.

★ Agent data acquisition

An AI agent can acquire data autonomously through Graunt: searching public listings, running a buy preflight, purchasing a listing, and downloading the resulting entitlement as a machine ZIP or an LLM-ready pack. Scoped agent credentials keep the agent's reach to purchase and download routes. Connected through Jentic, the agent calls only the operations its rule allows.

Search listings for a topic, purchase the best match, and download its entitlement as a machine ZIP

Entitlement delivery and access control

Buyers need to hand packet access to downstream systems without sharing a master credential. Graunt issues durable packet access keys and short-lived access passes bound to a single entitlement, each read-only and surfaced once at creation. An agent can mint, list, and revoke these so access stays auditable.

Mint a read-only access pass for an owned entitlement and then revoke it when the task finishes

Seller listing publication

Data sellers list packets for sale by creating a packet upload session, registering assets with presigned PUT URLs, and finalizing a frozen bundle revision before submitting the listing for review. Graunt validates and hashes the bundle on finalize. An agent can drive this pipeline end to end for a catalog of datasets.

Create a packet upload session, register an asset, finalize the bundle, and create a listing for it

Key Endpoints

183 endpoints — the graunt api runs a marketplace for agent-ready data packets, where listings expose stable ids, declared rights, provenance, pricing, and manifest references.

METHOD

PATH

DESCRIPTION

GET

/v1/listings

Search active listings

GET

/v1/listings/{id}

Fetch a public listing detail

POST

/v1/purchases

Initiate a full purchase of a listing

GET

/v1/entitlements/{id}/download

Fetch a presigned download URL for an owned entitlement

POST

/v1/access-passes

Create a Graunt Access Pass

POST

/v1/datasets

Upload a dataset file with metadata

GET

/v1/receipts

List receipts for the auth org

GET

/v1/listings

Search active listings

GET

/v1/listings/{id}

Fetch a public listing detail

POST

/v1/purchases

Initiate a full purchase of a listing

GET

/v1/entitlements/{id}/download

Fetch a presigned download URL for an owned entitlement

POST

/v1/access-passes

Create a Graunt Access Pass

POST

/v1/datasets

Upload a dataset file with metadata

GET

/v1/receipts

List receipts for the auth org

Why Jentic?

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

Setup

Wiring Graunt by hand means juggling several Bearer token types, a user JWT, a scoped agent token, access-pass and packet-access-key tokens, and the Stripe payment flow yourself. Through Jentic you install once, import Graunt from the API Directory, store the token once, and your agent calls it.

Permission scoping

Graunt puts the entitlement id in the URL path (/v1/entitlements/{id}/...), so a rule can pin your agent to one entitlement and its download and query operations. You choose the operations it may call, so publishing or refund operations are not included unless you add them.

Credential isolation

Your Graunt token 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 'buy a data listing' or 'download an entitlement', and Jentic returns the matching Graunt operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using Graunt API through Jentic.

What authentication does the Graunt API use?

Graunt uses Bearer tokens in the Authorization header, per its OpenAPI spec: a user JWT from login, a scoped agent Bearer token for the agent purchase and listing routes, and short-lived access-pass or packet-access-key Bearer tokens for read-only packet access. A scoped X-API-Key app credential is also defined. Public listing endpoints need no credential. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at execution time.

Can I buy and download a data packet with the Graunt API?

Yes. The purchase operation buys an active listing and creates an entitlement, and the entitlement download operation returns a presigned URL for the packet. You can also pull a bundle as a signed-URL list, a source archive, a machine ZIP, or an LLM-ready pack.

What are the rate limits for the Graunt API?

The OpenAPI spec does not publish fixed rate limits, though some public operations such as free-access grants are noted as rate-limited. Check https://graunt.com for current limits.

How do I buy and download a packet with the Graunt API through Jentic?

Search Jentic for 'buy a data listing' and it returns the Graunt purchase operation with its input schema, then search 'download an entitlement' for the download operation. Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, import Graunt from the API Directory, and store your token once. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Can I limit what my agent is allowed to do with Graunt?

Yes. Scope the agent to one entitlement: Graunt puts the entitlement id in the URL path (/v1/entitlements/{id}/...), so a rule can let the agent download and query that packet and touch no other, and every call it makes is logged.

Is there a Graunt MCP server?

You don't need an MCP server to connect your agent to Graunt. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent discovers and calls the operations it needs on demand.

Graunt API

AI ReadinessFoundational (C)53/100

See full scorecard

Official vendor OpenAPI document · agent-readyE CommerceStorefrontbearer183 EndpointsREST

For Agents

Lets an AI agent search and buy agent-ready data packets, receive entitlements, download packet assets via signed URLs, and query entitled content.

Use for: Search for data packets that match a topic, I want to buy a listing and get its entitlement, Download the packet behind an entitlement I own, Mint a read-only access pass for an entitled packet

Not supported: Does not handle model training, data labeling, or general cloud file storage. Use for buying and selling agent-ready data packets only.

The Graunt API runs a marketplace for agent-ready data packets, where listings expose stable IDs, declared rights, provenance, pricing, and manifest references. Buyers purchase a listing to receive an entitlement, then download the packet as a signed-URL list, source archive, or machine ZIP, or ask sourced-answer queries over it. Sellers publish listings through packet upload sessions, and payment runs through Stripe with money values expressed in integer cents.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: D+Signals: 4

89%

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.

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: DSignals: 4

35%

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.

53%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: C-Signals: 1

51%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

61%

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

75%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Graunt API to your agent

Capabilities

Start building with Graunt API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Graunt API

Jentic AI Readiness Score

Graunt 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