canonical: https://jentic.com/apis/doit.com/doit

# DoiT API

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.

## For AI 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.

## Scope

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

## Capabilities

- 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
- List cloud incidents and service quotas across connected cloud accounts

## Use cases

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

Example prompt: 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.

Example prompt: 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.

Example prompt: 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.

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

## Key endpoints

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

## Key resources

- **Reports** — List, create, run, and query saved and ad-hoc cost reports, including async report runs
- **Budgets** — Create and track budgets and act on budget suggestions
- **Anomalies** — List cost anomalies, review their status, and read explanations
- **Billing** — Retrieve invoices, billing explainers, assets, and contract templates
- **IAM** — Manage users, roles, organizations, and service-account API tokens

## 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:** 61 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 73 / 100
  - Developer Experience & Jentic Compatibility: 67 / 100
  - AI-Readiness & Agent Experience: 64 / 100
  - Agent Usability: 43 / 100
  - Security: 63 / 100
  - AI Discoverability: 80 / 100
- **View full report:** https://jentic.com/apis/doit.com/doit/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 <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **AWS Cost Explorer** — AWS-native cost and usage analysis for a single cloud, versus DoiT's multi-cloud cost view.
- **Google Cloud Billing** — Google Cloud's own billing accounts and budgets, which DoiT aggregates alongside other providers.
- **New Relic** — Observability and performance data that pairs with DoiT's cost and incident view.

## FAQ

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