Install Jentic One Beta

Connect the Dribba Public API to your agent

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

Fetch the studio's company profile, service catalog, and individual services

Read case studies, the blog index, and open job positions

Request a ballpark project estimate from the estimator inputs

Run several read operations in one batched request

Start a markdown export of the site and read the finished result

GET STARTED

Start building with Dribba Public API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Dribba Public API for, with concrete tasks.

★ Agent-driven studio research

An AI agent connected through Jentic reads Dribba's company profile, service catalog, and case studies to answer questions about what the studio does and has built, returning structured facts rather than scraping the website. Because the data is JSON with stable fields, the agent can cite specific services and cases directly.

Fetch the company profile and service catalog and summarize what the studio offers

Project estimate automation

A sales or intake workflow calls the estimator endpoint with project inputs to return a ballpark estimate without a human quoting it by hand. The estimator inputs endpoint exposes the parameters the estimate accepts, so an agent can gather them first and then request the figure.

Read the estimator inputs, then request a ballpark estimate for a described project

Site content export

Teams that want the studio's content as portable text start an asynchronous markdown export, poll the job, and read the finished markdown. Dribba runs the export as a job and returns a result endpoint so an agent can wait for completion before pulling the output.

Start a markdown export, poll the job until it finishes, and read the exported content

Case study and comparison lookup

Content and research workflows pull individual case studies and technology comparison entries by slug to drop concrete examples into a report. The API returns one case study or comparison per slug, giving an agent a precise, citable record rather than a page of HTML.

Fetch a specific case study by its slug and return its summary and outcome

Key Endpoints

26 endpoints — the dribba public api exposes the content behind dribba.

METHOD

PATH

DESCRIPTION

GET

/api/v1/company

Read the company profile

GET

/api/v1/services

List the service catalog

GET

/api/v1/cases

List case studies

GET

/api/v1/articles

Read the blog index

GET

/api/v1/jobs

List open positions

POST

/api/v1/estimate

Request a ballpark project estimate

POST

/api/v1/batch

Run several read operations in one request

GET

/api/v1/company

Read the company profile

GET

/api/v1/services

List the service catalog

GET

/api/v1/cases

List case studies

GET

/api/v1/articles

Read the blog index

GET

/api/v1/jobs

List open positions

POST

/api/v1/estimate

Request a ballpark project estimate

POST

/api/v1/batch

Run several read operations in one request

Why Jentic?

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

Setup

Wiring Dribba by hand still means reading its spec, choosing the production or sandbox host, and parsing its RFC 9457 problem responses yourself. Through Jentic you install once, import Dribba from the API Directory, and your agent calls it: there is no key to configure because every operation is public and read-only.

Permission scoping

Every Dribba operation is public and read-only, so a rule can allow your agent just the read operations it needs, such as fetching services or case studies. There are no write operations against your own data to grant.

Credential isolation

Dribba is a public, read-only API that needs no key, so there is nothing for Jentic to hold or inject. Your agent calls it directly through your own Jentic One instance.

Intent-based discovery

Agents search Jentic by intent such as 'fetch studio services' or 'request a project estimate', and Jentic returns the matching Dribba operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Dribba Public API through Jentic.

What authentication does the Dribba Public API use?

The Dribba Public API requires no authentication per its OpenAPI spec. Every operation is public and read-only, so your agent can call it without a key. Errors come back as RFC 9457 problem details with a stable code and a resolution hint.

Can I read the studio's services and case studies with the Dribba API?

Yes. The API returns the company profile, the service catalog, individual services by slug, case studies, the blog index, open jobs, and technology comparisons, all as structured JSON you can read directly.

What are the rate limits for the Dribba Public API?

The spec advertises IETF RateLimit fields on every response so your client can read the current allowance as it goes. Check those headers and the Dribba documentation for the exact per-client limit rather than hardcoding a number.

Is there a Dribba API MCP server?

You don't need an MCP server to give your agent the Dribba Public API. Jentic connects it directly from the API Directory: import it and your agent reads the content it needs on demand, without loading another server's tool definitions into its context.

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

Yes. Every operation is public and read-only, so a rule can allow your agent just the read operations it needs, such as fetching services or case studies, and deny the rest, with every call logged for review.

How do I read Dribba's content through Jentic?

Search Jentic for 'fetch studio services and case studies', add the Dribba API from the directory, and your agent can call it right away since it needs no credential. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Dribba Public API

AI ReadinessAI-Ready (A)84/100

See full scorecard

Official vendor OpenAPI document · agent-readyMarketingContent Managementnone26 EndpointsREST

For Agents

Fetch a product studio's company profile, services, case studies, blog, and jobs as JSON, request a project estimate, and export the site as markdown.

Use for: Get the studio's company profile, List the services Dribba offers, Show me the published case studies, Find the open job positions

Not supported: Does not manage your own content, authenticate users, or process payments. Use for reading one studio's public content and requesting estimates only.

The Dribba Public API exposes the content behind dribba.com, a digital product studio, as structured JSON: company profile, service catalog, case studies, blog articles, open jobs, and technology comparisons. It also offers a project estimator, a batch endpoint that runs several read operations in one request, and an asynchronous markdown export of the site. Every operation is public and, per the spec, read-only, returning RFC 9457 problem details on errors and advertising IETF RateLimit fields on each response.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

98%

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

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

75%

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

77%

Description Coverage

Coverage of descriptions across API elements.

100%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

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

52%

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.

100

Security

Trust, risk posture, and security compliance.

Grade: A+Signals: 1

100%

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

71%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Dribba Public API to your agent

Capabilities

Start building with Dribba Public API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Dribba Public API

Jentic AI Readiness Score

Dribba Public 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