Install Jentic One Beta

Connect the GoldBean API to your agent

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

Generate chat completions through an OpenAI-compatible endpoint

Create text embeddings for semantic search

Generate images from text prompts

Transcribe audio to text and synthesize speech from text

Run OCR on images, including ID card and high-accuracy modes

GET STARTED

Start building with GoldBean API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use GoldBean API for, with concrete tasks.

★ Agent Multimodal Inference

An AI agent connected through Jentic reaches several model types through one GoldBean integration, calling chat completions for reasoning, embeddings for retrieval, and image or speech endpoints for generation as a task requires. Because the surface is OpenAI-compatible, the agent uses familiar request shapes while GoldBean handles the pay-per-call settlement.

Generate a chat completion for a prompt, then create embeddings for the same text and report both results

Pay-Per-Call OCR and Translation

A document workflow runs OCR on a scanned page and translates the extracted text, paying only for the calls it makes. The Baidu-backed OCR and translation endpoints are reached directly, so the workflow needs no separate OCR vendor and translation vendor.

Run OCR on an image to extract text, then translate the extracted text into English

OpenAI-Compatible Chat and Embeddings

A retrieval-augmented app points its existing OpenAI-style client at GoldBean to generate embeddings for its corpus and chat completions over the retrieved context. Listing the available models first lets the app pick a supported model before sending inference requests.

List the available models, generate embeddings for a document set, and run a chat completion over the retrieved context

Key Endpoints

37 endpoints — the goldbean api provides pay-per-call access to a range of ai models, bridging baidu ai capabilities to an openai-compatible surface.

METHOD

PATH

DESCRIPTION

POST

/v1/chat/completions

Chat completions, OpenAI-compatible

POST

/v1/embeddings

Generate embeddings

POST

/v1/images/generations

Generate an image from a prompt

POST

/v1/audio/transcriptions

Transcribe audio to text

POST

/v1/audio/speech

Synthesize speech from text

GET

/paid/baidu-ocr

Run Baidu OCR on an image

GET

/paid/baidu-translate

Translate text with Baidu

GET

/v1/models

List available models

POST

/v1/chat/completions

Chat completions, OpenAI-compatible

POST

/v1/embeddings

Generate embeddings

POST

/v1/images/generations

Generate an image from a prompt

POST

/v1/audio/transcriptions

Transcribe audio to text

POST

/v1/audio/speech

Synthesize speech from text

GET

/paid/baidu-ocr

Run Baidu OCR on an image

GET

/paid/baidu-translate

Translate text with Baidu

GET

/v1/models

List available models

Why Jentic?

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

Setup

Wiring the GoldBean API by hand means handling its x402 pay-per-call protocol, settling USDC on Base for each paid request, and keeping the free system endpoints separate from the paid inference ones. Through Jentic you install once, import GoldBean from the API Directory, store the payment credential once, and your agent calls it.

Permission scoping

GoldBean exposes each model as its own path (/v1/chat/completions, /paid/baidu-ocr), so a rule can pin your agent to just the inference operations you pick, such as chat completions and embeddings. You choose the operations it may call, so costly image or speech generation is not included unless you add it.

Credential isolation

Your GoldBean payment credential 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 'generate a chat completion' or 'run OCR on an image', and Jentic returns the matching GoldBean operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using GoldBean API through Jentic.

How does the GoldBean API handle authentication and payment?

The GoldBean API uses the x402 pay-per-call protocol per its OpenAPI spec: paid inference endpoints settle in USDC on Base, while system endpoints such as health, service info, and model listing need no payment. Through Jentic the payment credential is stored encrypted by your own Jentic One instance and injected at call time, so it never reaches the agent's context.

Can I use the GoldBean API with OpenAI-compatible clients?

Yes. The chat completions, embeddings, image generation, speech, and transcription endpoints follow the OpenAI request shape, and a models endpoint lists what is available. An existing OpenAI-style client can point at GoldBean's base URL with little change.

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

Yes. GoldBean exposes each model as its own path, so write a rule that allows only the inference operations you pick, such as chat completions and embeddings, so costly image or speech generation is not included unless you add it. Every call the agent makes is logged, which matters when each paid call spends USDC.

What are the rate limits for the GoldBean API?

The OpenAPI spec does not state request rate limits for the GoldBean API; access is pay-per-call, so cost rather than a fixed ceiling governs usage. Check the GoldBean documentation and its pricing endpoints for the current per-endpoint prices.

How do I generate a chat completion with the GoldBean API through Jentic?

Search Jentic for 'generate a chat completion' and it returns the chat completions operation with its input schema; your agent sends the prompt and reads back the model's response. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Is there a GoldBean MCP server?

You don't need a separate server to give your agent the GoldBean API. Jentic connects it directly from the API Directory: import it, store your payment credential once, and your agent calls the inference operations with scoping and credential isolation applied.

Goldbean Api Xyz GoldBean API

AI ReadinessNon-Ready (F)0/100

See full scorecard

Official vendor OpenAPI document · agent-readyAI/MLLanguage Modelsx40237 EndpointsREST

For Agents

Call pay-per-call AI inference over an OpenAI-compatible surface: chat completions, embeddings, image generation, speech, transcription, OCR, and translation backed by Baidu models. Payments settle in USDC on Base via x402.

Use for: I need to generate a chat completion, Create embeddings for a batch of text, Generate an image from a prompt, Transcribe an audio file to text

Not supported: Does not handle model training, fine-tuning, or vector storage. Use for pay-per-call inference across Baidu-backed AI models for text, image, speech, and OCR only.

The GoldBean API provides pay-per-call access to a range of AI models, bridging Baidu AI capabilities to an OpenAI-compatible surface. It generates chat completions and embeddings, creates images from text prompts, transcribes audio and synthesizes speech, and runs OCR, translation, and NLP through Baidu-backed endpoints. Paid inference endpoints settle in USDC on Base using the x402 protocol, while system endpoints such as health and model listing are free.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

97%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

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

100%

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

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

39%

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

63%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

89%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

49%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1

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: CSignals: 1

55%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the GoldBean API to your agent

Capabilities

Start building with GoldBean API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Goldbean Api Xyz GoldBean API

Jentic AI Readiness Score

GoldBean 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