canonical: https://jentic.com/apis/dribba.com/dribba # Dribba Public API 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. ## For AI 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. ## Scope Does not manage your own content, authenticate users, or process payments. Use for reading one studio's public content and requesting estimates only. ## Capabilities - 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 - Compare technologies through the published comparison entries ## Use cases ### 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. Example prompt: 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. Example prompt: 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. Example prompt: 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. Example prompt: Fetch a specific case study by its slug and return its summary and outcome ## Key endpoints | 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 | ## Key resources - **Company** — Read the studio's company profile - **Services** — List the service catalog and fetch one service by slug - **Cases** — List case studies and fetch one by slug - **Content** — Read the blog index, open jobs, and technology comparisons - **Estimate** — Read estimator inputs and request a ballpark project estimate - **Exports** — Start a markdown export and read the finished result ## AI readiness 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. - **Score:** 84 / 100 - **Maturity:** AI-Ready - **Dimensions:** - Foundational Compliance: 100 / 100 - Developer Experience & Jentic Compatibility: 69 / 100 - AI-Readiness & Agent Experience: 82 / 100 - Agent Usability: 94 / 100 - Security: 100 / 100 - AI Discoverability: 71 / 100 - **View full report:** https://jentic.com/apis/dribba.com/dribba/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **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 handling:** 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. - **Discovery method:** 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. ## Related APIs - **Contentful** — A headless CMS delivering structured content via API, versus Dribba's fixed studio content surface. - **Sanity** — A content platform with a query API, an alternative source of structured content to Dribba. - **Prismic** — A headless CMS for website content that pairs with Dribba's read-only studio content. ## FAQ ### 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.