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

# 7275 DEXUN AdWhiz API

The DEXUN AdWhiz API reports the authenticated caller's identity and plan quota, the current rate-limit window, and a stream of security audit events recorded for the account. It lists the API keys issued to the caller and serves a public product changelog feed. An agent can confirm who a key belongs to and how much of its subscription tier remains before it spends the allowance on other work.

## For AI agents

Read the caller's identity, plan quota, rate-limit window, and account audit events, and list the issued API keys. All five operations are read-only GETs secured with a bearer API key.

## Scope

Does not handle ad campaign creation, billing changes, or key rotation. Use for reading account identity, quota, and audit activity only.

## Capabilities

- Identify the authenticated caller and read their plan quota from the whoami endpoint
- Check the current rate-limit window and remaining allowance without making a probe call
- Stream the security audit events recorded for the account
- List the API keys issued to the caller
- Read the public product changelog feed

## Use cases

### Quota-Aware Rate Management

Before an agent spends its allowance on a batch of calls, it reads the current rate-limit window from DEXUN AdWhiz and decides whether to proceed, pause, or back off. The usage endpoint returns the remaining allowance without consuming a probe request, so the agent can pace itself against its subscription tier rather than discovering the limit by hitting a 429.

Example prompt: Call GET /usage to read the current rate-limit window, then decide whether to continue issuing calls

### Account Audit Monitoring

Security-conscious workflows poll DEXUN AdWhiz for the stream of audit events recorded against the account, surfacing new key activity or sensitive actions for review. The agent reads the event stream and the list of issued keys so it can flag anything unexpected to a human operator.

Example prompt: Call GET /audit-events to pull recent account activity, then GET /api-keys to confirm which keys are active

### AI Agent Integration via Jentic

An AI agent reaches DEXUN AdWhiz through Jentic without handling the bearer key itself. It searches by intent, receives the matching operation and its input schema, and executes the call with the credential injected at run time. This lets the agent check identity, quota, and audit activity as a preflight step before running larger tasks.

Example prompt: Search Jentic for 'check my API quota', load the GET /usage schema, and execute it with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/me` | Identity and quota whoami |
| GET | `/usage` | Read the current rate-limit window |
| GET | `/audit-events` | Stream security audit events for the caller |
| GET | `/api-keys` | List the caller's API keys |
| GET | `/changelog` | Public product changelog feed |

## Key resources

- **Identity and Quota** — Read the caller's identity and remaining plan quota via /me and /usage
- **Activity** — Read the account's security audit event stream via /audit-events
- **Keys** — List the API keys issued to the caller via /api-keys

## 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:** 45 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 62 / 100
  - AI-Readiness & Agent Experience: 19 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 88 / 100
- **View full report:** https://jentic.com/apis/7275.com/7275/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 DEXUN AdWhiz by hand means sending its bearer API key to app.7275.com/api/v1 and reading the X-RateLimit headers on every response yourself. Through Jentic you install once, import DEXUN AdWhiz from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** This API is read-only: every operation is a GET, so a rule can confine your agent to reading its own quota and audit events and nothing that changes account state. You choose which of the five reads it may call, so the usage check can be allowed while the API-key listing is withheld.
- **Credential handling:** Your DEXUN AdWhiz 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 'check my API quota' or 'read account audit events', and Jentic returns the matching DEXUN AdWhiz operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Better Stack** — Broader observability platform covering uptime, logs, and incident monitoring
- **Cronitor** — Cron job and uptime monitoring with alerting
- **Statuspage** — Public status pages for communicating service health

## FAQ

### What authentication does the DEXUN AdWhiz API use?

The DEXUN AdWhiz API authenticates with a bearer API key in the Authorization header per its OpenAPI spec, using dxk_live_ or dxk_test_ keys generated in the API-keys settings. The public changelog endpoint is open. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at execution time, so it never reaches the agent.

### What are the rate limits for the DEXUN AdWhiz API?

Rate limits depend on the subscription tier: 60, 120, 600, or 3000 requests per minute per key, per the OpenAPI spec, and every authenticated response carries X-RateLimit headers. The usage endpoint reports the current window so an agent can read its remaining allowance without a probe call.

### Can I read my account audit events with the DEXUN AdWhiz API?

Yes. The GET /audit-events operation returns the stream of security audit events recorded for the caller, and GET /api-keys lists the keys issued to the account. The responses are structured JSON an agent can parse and act on directly.

### How do I check my quota with the DEXUN AdWhiz API through Jentic?

Search Jentic for 'check my API quota', and it returns the DEXUN AdWhiz usage operation with its input schema. Load the schema and execute GET /usage with the credential injected at run time. To run it on your own infrastructure, install Jentic One from its GitHub repo.

### Can I limit what my agent is allowed to do with the DEXUN AdWhiz API?

Yes. Write a rule that allows only the reads it needs, for example the quota and audit-event lookups, so the agent can observe account state and nothing more. Because every call it makes runs through your own instance, each one is logged for you to review.