Install Jentic One Beta

Connect the DoiT API to your agent

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

Run saved and ad-hoc cost reports and query them by dimension, allocation, and time range

Create budgets, track spend against them, and accept or dismiss budget suggestions

List cost anomalies and read the explanation behind each one

Retrieve billing invoices and per-payer billing explainers

Manage users, roles, and service-account API tokens for your DoiT organization

GET STARTED

Start building with DoiT API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use DoiT API for, with concrete tasks.

★ Agent-driven cloud cost monitoring

An AI agent connected through Jentic watches DoiT for cost anomalies and budget overruns, listing flagged anomalies, reading their explanations, and checking budget status so a team hears about unexpected spend without logging into a dashboard. The agent reads the anomaly and budget data on demand and summarizes what changed.

List cost anomalies flagged in the last 7 days, retrieve the explanation for each, and report which connected account they belong to

Budget tracking and suggestions

Finance and platform teams use the DoiT API to create budgets, track actual spend against them, and review DoiT's budget suggestions. The API returns each budget's configuration and current status, and exposes accept and dismiss actions for suggestions so budgets stay current as usage shifts.

List all budgets, identify which are above 90 percent of their limit, and report their names and current spend

Invoice retrieval and reconciliation

Billing teams pull invoices and per-payer billing explainers from DoiT to reconcile cloud charges against internal records. The billing endpoints return invoices by month and a billing explainer that breaks a payer's charges down, giving an agent the figures it needs to match against an accounting system.

Retrieve the invoices for the current billing month and return each invoice id, total, and payer

Cost report querying

Analysts run cost reports through the DoiT API, either by listing saved reports or by posting an ad-hoc query, to break cloud spend down by dimension and allocation. Async report runs return an operation handle that the agent polls for results, so large queries complete without blocking.

Run a cost query grouped by service for the last 30 days and return the top five services by spend

Key Endpoints

246 endpoints — the doit api provides programmatic access to the doit cloud financial management platform, returning cost and usage reports, budgets, cost anomalies, invoices, and cloud incident data across connected aws and google cloud accounts.

METHOD

PATH

DESCRIPTION

GET

/analytics/v1/reports

List saved cost reports

POST

/analytics/v1/reports/query

Run an ad-hoc cost query

GET

/analytics/v1/budgets

List budgets

GET

/anomalies/v1

List cost anomalies

GET

/billing/v1/invoices

List invoices

GET

/core/v1/cloudincidents

List cloud incidents

GET

/iam/v1/users

List users

GET

/analytics/v1/reports

List saved cost reports

POST

/analytics/v1/reports/query

Run an ad-hoc cost query

GET

/analytics/v1/budgets

List budgets

GET

/anomalies/v1

List cost anomalies

GET

/billing/v1/invoices

List invoices

GET

/core/v1/cloudincidents

List cloud incidents

GET

/iam/v1/users

List users

Why Jentic?

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

Setup

Wiring the DoiT API by hand means learning its API key auth in the Authorization header, adding the X-Tenant-Id header for tenant-scoped calls, and handling idempotency keys on the async report and billing actions yourself. Through Jentic you install once, import DoiT from the API Directory, store the key once, and your agent calls it.

Permission scoping

DoiT carries report, budget, and anomaly ids in the URL path, so a rule can pin your agent to the operations you pick, such as reading reports and budgets. You choose the operations it may call, so destructive ones like deleting a report or canceling a contract are not included unless you add them.

Credential isolation

Your DoiT 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 'list cloud cost anomalies' or 'run a cost report', and Jentic returns the matching DoiT operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using DoiT API through Jentic.

What authentication does the DoiT API use?

The DoiT API authenticates with an API key sent in the Authorization header per its OpenAPI spec, with an X-Tenant-Id header for tenant-scoped calls, and it also declares an OAuth flow. A few public signup endpoints need no credential. Through Jentic the key is stored once and injected at call time so it never lands in your agent's prompt.

Can I run cost reports with the DoiT API?

Yes. You can list saved reports, run an ad-hoc cost query to break spend down by dimension and allocation, and poll async report runs for results. The analytics endpoints also return dimensions, allocations, and widgets to build the query against.

What are the rate limits for the DoiT API?

The OpenAPI specification does not state rate limits. Check your DoiT plan and the DoiT developer documentation for the limits that apply to your account before running high-volume report queries.

Is there a DoiT API MCP server?

You don't need an MCP server to give your agent the DoiT API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls the cost, budget, and billing operations 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 DoiT API?

Yes. Write a rule that allows only the report-read and budget-read operations, so the agent can pull cost reports and check budgets but cannot create, update, or delete them, and every call it makes is logged for review.

How do I monitor cloud cost anomalies with the DoiT API through Jentic?

Search Jentic for 'list cloud cost anomalies', add the DoiT API from the directory, and store your key once; your agent can then list anomalies and read each explanation on demand. To run it on your own infrastructure, install Jentic One from its GitHub repo.

DoiT API

AI ReadinessAI-Aware (B-)61/100

See full scorecard

Official vendor OpenAPI document · agent-readyAnalyticsBusiness IntelligenceapiKey, oauth2246 EndpointsREST

For Agents

Query cloud cost and usage reports, track budgets, surface cost anomalies, and retrieve invoices across connected AWS and Google Cloud accounts through the DoiT platform.

Use for: I need to pull last month's cloud spend grouped by service, Show me the cost anomalies flagged this week, Check whether my project is tracking over budget, List all invoices for the current billing month

Not supported: Does not provision cloud compute, manage DNS, or process payments. Use for cloud cost analytics, budgeting, and billing data only.

The DoiT API provides programmatic access to the DoiT cloud financial management platform, returning cost and usage reports, budgets, cost anomalies, invoices, and cloud incident data across connected AWS and Google Cloud accounts. It runs saved and ad-hoc cost queries, tracks budgets and acts on budget suggestions, and manages users, roles, and service-account tokens for your organization. Billing endpoints return invoices and per-payer billing explainers, while the analytics endpoints drive reports, dimensions, allocations, and widgets.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

94%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

98%

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).

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

Example Density

How richly the API is illustrated with examples.

97%

Example Validity

Percentage of examples that conform to their schemas.

67%

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

74%

Description Coverage

Coverage of descriptions across API elements.

22%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

99%

OperationId Quality

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

60%

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

63%

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

80%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the DoiT API to your agent

Capabilities

Start building with DoiT API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

DoiT API

Jentic AI Readiness Score

DoiT 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