Install Jentic One Beta

Connect the DEXUN AdWhiz API to your agent

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

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

GET STARTED

Start building with DEXUN AdWhiz API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use DEXUN AdWhiz API for, with concrete tasks.

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

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.

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.

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

Key Endpoints

5 endpoints — 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.

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

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

Why Jentic?

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

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using DEXUN AdWhiz API through Jentic.

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.

7275 DEXUN AdWhiz API

AI ReadinessFoundational (D)45/100

See full scorecard

Official vendor OpenAPI document · agent-readyDeveloper ToolsMonitoring Observabilitybearer5 EndpointsREST

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

Use for: Check whether my API key is still within its rate-limit window, Get the identity and plan quota for the current key, List the API keys issued to my account, Monitor the security audit events on my account

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

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.

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

99%

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.

45%

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

31%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

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

45%

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.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

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

88%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the DEXUN AdWhiz API to your agent

Capabilities

Start building with DEXUN AdWhiz API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

7275 DEXUN AdWhiz API

Jentic AI Readiness Score

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