How AI Agents Can Use the WealthGlider API

WealthGlider has been designed so an AI agent can retrieve WealthGlider Premium research for its human owner. The agent can bring that research, insights, and recommendations into the human owner's daily workflow and decide what is suitable for that person.

What An Agent Can Request

With the appropriate scope, an authorized agent will be able to request:

the latest published market-day edition;
one exact historical date at a time for a Premium account;
one exact immutable edition revision;
one symbol from an exact edition;
aggregate performance data for published WealthGlider recommendations; and
the account's current API allowance and usage.

The approved scopes are:

daily_recommendations:read for the latest edition;
historical_recommendations:read for a single date, edition, signal, or aggregate performance request; and
account:read for entitlement and usage information.

An account owner should grant only the scopes the integration actually needs. Trial accounts may use daily access but do not receive historical access.

What An Agent Cannot Request

The API does not provide:

date ranges or several dates in one request;
archive pagination or bulk export;
a symbol's entire recommendation history;
brokerage connections, order entry, or trade execution; or
personalized advice based on a portfolio or financial situation.

Historical access accepts one YYYY-MM-DD date. An agent that needs another date must make another explicit request, subject to the account-wide allowance and rate limit.

The Human Stays In Control

The account owner—not the agent—signs in to WealthGlider, purchases Premium access, names a credential, chooses its minimum scopes, and copies the secret once. Subscription changes and credential creation, revocation, or replacement remain human-controlled actions.

A real secret must never appear in a prompt, chat transcript, URL, source file, screenshot, analytics event, or log. Store it in an approved secret store and send it only in an HTTPS Authorization header:

Authorization: Bearer $WEALTHGLIDER_API_KEY

The placeholder above is not a usable credential.

Try The Public Sample Now

The unauthenticated sample uses fictional WGDEMO* symbols. It demonstrates the response shape; it is not a live recommendation edition.

curl --fail-with-body \
  https://api.wealthglider.com/v1/samples/latest

Confirm that data_kind is sample before displaying or processing the result.

Authenticated Request Examples

These requests use the production contract. A human account owner must create the credential before an agent can run them.

Request the latest edition:

curl --fail-with-body \
  -H "Authorization: Bearer $WEALTHGLIDER_API_KEY" \
  https://api.wealthglider.com/v1/editions/latest

Avoid consuming an allowance when nothing has changed by sending the last ETag:

curl --fail-with-body \
  -H "Authorization: Bearer $WEALTHGLIDER_API_KEY" \
  -H 'If-None-Match: "previous-etag"' \
  https://api.wealthglider.com/v1/editions/latest

Request one exact historical date:

curl --fail-with-body \
  -H "Authorization: Bearer $WEALTHGLIDER_API_KEY" \
  https://api.wealthglider.com/v1/editions/by-date/2026-08-28

Inspect account usage:

curl --fail-with-body \
  -H "Authorization: Bearer $WEALTHGLIDER_API_KEY" \
  https://api.wealthglider.com/v1/account/usage

Allowances And Fair Use

The approved launch model gives each account 50 successful authenticated recommendation-data responses per calendar month, shared across all of its credentials. Warning headers begin at 40, and the API returns HTTP 429 at 50. There is no automatic overage billing.

The burst limit is five authenticated data requests per account per 60 seconds. Agents should respect Retry-After and must not create extra credentials to evade an account-wide limit.

An account-usage read, invalid request, missing resource, or 304 Not Modified response does not consume the monthly recommendation-data allowance.

Check Every Response

Before an agent uses a result, it should verify:

schema_version is supported by the integration;
data_kind is live for authenticated recommendations or sample for the fictional sample;
edition.edition_date is the expected market date;
edition.edition_id is the expected immutable revision;
the result is not stale or a fallback from an older date; and
the required recommendation fields and driver evidence are populated.

Corrections create a new immutable revision such as 2026-08-28.r2. An integration must not silently overwrite or merge revisions.

Handle Failures Explicitly

Authentication, missing scope, entitlement, monthly allowance, burst limit, missing publication, and service failures are different states. An agent should explain the specific failure and approved recovery information without substituting old data and calling it current.

Keep the non-sensitive X-Request-Id when contacting support. Never include the credential itself. Subscription and credential decisions belong to the human account owner.

API Documentation

Use the Agent API guide for a human-readable integration walkthrough. Use the OpenAPI specification as the machine-readable source of truth for operations, parameters, authentication, and response schemas.

Additional resources:

For support, email support@wealthglider.com without sending credential material.