Developer Reference
Aware Signals API Reference
Base URL, authentication, starter request, data depth, trial limits, record behavior, coverage, full pricing and licensing, production access, and developer resource links.
01 · Quickstart
Make the first request
- Base URL
https://api.iamaware.us/v1/- Documentation
https://api.iamaware.us/v1/docsCurrent field reference, action-type guidance, and browser-based live console.- Current version path
/v1- Primary collection endpoint
GET /signalsUse the live docs for the complete current parameter list.
curl "https://api.iamaware.us/v1/signals?action_type=tariff&limit=5" \
-H "X-API-Key: YOUR_ACCOUNT_SPECIFIC_API_KEY"02 · Authentication
Authenticate every request with an account-specific key
X-API-Key: YOUR_ACCOUNT_SPECIFIC_API_KEY- Every customer or evaluation account receives its own key.
- Do not reuse one shared key across prospects, customers, or environments.
- Trial timing begins with the first successful API call for the standard evaluation flow.
- Keys are revocable and should be rotated immediately if exposed.
03 · Data model
Available data depth
Essential, Structured, and Full data depth are available. The live docs remain authoritative for exact JSON key names, types, nullability, and enum values.
| Depth | Current content | Use |
|---|---|---|
| Essential | Government action or event, relevant dates, actor, jurisdiction, action type, headline, summary, primary or originating source. | Core ingestion, alerts, models, dashboards, and source-traceable workflows. |
| Structured | Richer normalized fields, expanded entities, affected categories, and stronger filtering than Essential. Use the live docs for the exact current field list. | Integration-ready workflows that need more structure without the full enrichment layer. |
| Full | Richest event context, including sector tags, commodity tags, region tags, orientation, severity, confidence, and other fields exposed in the live API. | Deeper filtering, classification, scoring, segmentation, and downstream modeling. |
Date semantics
The product distinguishes the event date from the effective date when the effective date is available. This separation is important for workflows that need lead time between announcement and business effect.
Source provenance
Signals are designed to preserve the primary or originating source. Downstream products should retain the source reference when traceability matters to the user.
04 · Querying
Use the live docs for the current supported filters
The approved starter request confirms action_type and limit on GET /signals. The documentation and browser console are the source of truth for the complete query surface, accepted values, pagination behavior, and any additional filters.
GET /v1/signals?action_type=tariff&limit=5For customer implementations, validate filters against the live docs before storing enum values or building user-facing filter controls.
05 · Standard evaluation limits
14-day evaluation behavior
| Dimension | Standard evaluation |
|---|---|
| Duration | 14 calendar days, beginning with the first successful API call. |
| Data depth | Essential. |
| Distinct record allowance | Up to 250 distinct Signal records. |
| History | Rolling 30-day window. |
| Rate limit | 120 requests per minute. |
| Scope | One company, one development or evaluation environment, one defined use case. |
| Rights | Evaluation only. No production use, redistribution, resale, model training, or permanent archive. |
Distinct-record accounting
- A Signal counts when it is first delivered to the key.
- Re-fetching a previously delivered record does not consume another distinct-record allowance.
- After the cap is reached, previously delivered records remain accessible.
- Delivery of new Signals pauses until access is expanded or converted.
Production rate limits, record volume, history, support, and environments are set by the production agreement rather than inherited from the trial.
06 · Coverage
Current coverage position
Describe the feed as U.S.-deep with selected global coverage. Current strength includes U.S. federal government action and selected global disruption feeds.
- Federal regulations and proposed rules.
- OFAC actions.
- USTR and Section 301 actions.
- Antidumping and countervailing duty actions.
- Bureau of Industry and Security actions.
- State Department designations.
- Restricted-party list changes.
- Selected global disaster events through GDACS.
07 · Data rights
API access and usage rights are separate
| Rights class | What it means |
|---|---|
| Internal Use | One organization uses Signals inside its own internal systems, models, products, dashboards, or workflows. |
| OEM / Embedding | Signals or derived outputs are embedded in customer-facing software. Requires separate OEM rights. |
| Advisor / Multi-Client | A consulting, legal, accounting, research, or advisory organization uses Signals across multiple clients. |
| Association Distribution | Signals or derived outputs are distributed across a member base or network. |
Raw-record redistribution, resale, permanent archive rights, model training, creation of a substitute database, white-label use, and downstream tenant access are not granted by silence. They must be explicitly included in the agreement.
08 · Production access
Production configuration is scoped to the actual integration
- Starting price
- $18,000 per year for production access.Website monthly starting option: $1,725 per month under an annual commitment.
- Pricing variables
- Data depth, record volume, usage rights, historical access, support or SLA, number of production environments, and implementation scope.
- Data depth
- Essential, Structured, and Full are available.
- History
- Longer history, archive access, and historical backfills are scoped separately. Do not assume the 30-day evaluation window defines production history.
- Implementation
- Technical discovery, configuration, schema mapping, testing, onboarding, and custom work may be quoted separately depending on complexity.
Use the full pricing and licensing framework below to size a production agreement. The final order should still state the exact data depth, volume allowance, usage rights, history, environments, support, and implementation scope.
09 · Pricing + licensing
Full pricing and licensing framework
Signals pricing separates five things that are easy to confuse: data depth, monthly record allowance, usage rights, historical access, and implementation. Essential, Structured, and Full are all available. The tables below are the commercial framework for production access.
Base production license by data depth and record allowance
| Data depth | Up to 1,500 records / month | Up to 4,000 records / month | Up to 8,000 records / month |
|---|---|---|---|
| Essential | $18,000 / year | $30,000 / year | $45,000 / year |
| Structured | $30,000 / year | $50,000 / year | $75,000 / year |
| Full | $50,000 / year | $80,000 / year | $120,000 / year |
Monthly billing under an annual commitment
The website pricing model uses a 15% annualized premium when the customer pays monthly instead of annually. Monthly billing does not automatically create month-to-month cancellation rights.
| Data depth | Up to 1,500 / month | Up to 4,000 / month | Up to 8,000 / month |
|---|---|---|---|
| Essential | $1,725 / month | $2,875 / month | $4,313 / month |
| Structured | $2,875 / month | $4,792 / month | $7,188 / month |
| Full | $4,792 / month | $7,667 / month | $11,500 / month |
Usage-right and license models
| License model | Starting commercial rule | Included / expansion logic |
|---|---|---|
| Internal Use | Base matrix above. | One defined organization or operating group using Signals inside its own systems and workflows. |
| Enterprise-wide Internal Use | Approximately 25% to 50% above the applicable base package. | Used when scope expands across subsidiaries, regions, or independently operating business units. Final adjustment depends on organizational reach, volume, and support burden. |
| OEM / Embedding | 1.5x the applicable Internal Use package, with a $30,000 annual minimum. | Includes a defined downstream customer or tenant allowance. Smaller downstream accounts may add approximately $1,500 to $5,000 per account per year. Larger partners use tenant bands, minimum commitments, or negotiated revenue share. |
| Advisor / Multi-Client | 1.5x the applicable Internal Use package. | Initial license may include up to five named clients. Additional clients may add approximately $3,000 to $7,500 per client per year. |
| Association Distribution | 1.25x the applicable Internal Use package for controlled summary distribution. | Price scales with member count, summary versus raw access, public versus member-only use, download rights, and member API access. Raw API access is custom. |
Raw-record redistribution, permanent archive rights, resale, model training, white-label use, substitute-database creation, direct downstream API access, and broader export rights require explicit terms and may materially increase price.
Historical access and archive pricing
| History model | Pricing | Commercial treatment |
|---|---|---|
| Standard evaluation history | Included | Rolling 30-day history during the standard 14-day evaluation. |
| Rolling production history | Reference inclusion: 90 days | Use as the commercial reference point, but confirm exact production availability and account configuration before contracting. |
| Existing production archive | 20% of annual Signals package | Ongoing access to the available archive, subject to confirmed coverage, data depth, and usage rights. |
| One-time archive export, Internal Use | 35% of annual package | Fixed JSON, CSV, or Parquet export. No ongoing updates. |
| One-time archive export, Advisor / Multi-Client | 60% of annual package | Client rights still need to be stated explicitly. |
| One-time archive export, OEM / Redistribution | 75% to 100% of annual package | Final price depends on downstream rights and distribution scope. |
Historical backfill before January 1, 2025
| Backfill scope | Starting price | Minimum |
|---|---|---|
| Narrow coverage | $10,000 per historical year | $15,000 |
| Standard coverage | $20,000 per historical year | $25,000 |
| Full coverage | $35,000 per historical year | $50,000 |
Depth multipliers for backfill: Essential 1.0x, Structured 1.25x, Full 1.5x. Historical backfill is a paid data-development project, not ordinary subscription history.
Onboarding and implementation
| Engagement | One-time starting range |
|---|---|
| Essential, standard integration | $3,000 to $5,000 |
| Structured integration | $5,000 to $10,000 |
| Full or complex enterprise integration | $10,000 to $25,000 |
| OEM or multi-client implementation | Custom, typically $15,000+ |
Implementation may include technical discovery, feed configuration, credentials and environments, coverage configuration, schema mapping, testing, technical onboarding, and initial support. Custom filters, delivery methods, SLAs, support, additional production environments, and security work may be priced separately.
Contract and billing model
- Annual commitment is the standard production model.
- Annual, quarterly, or monthly billing may be offered.
- Monthly billing does not automatically mean month-to-month cancellation.
- True month-to-month access is generally reserved for small early-access customers, narrow internal use, or strategic validation cases.
- OEM, multi-client, association, Full-depth, and major enterprise arrangements normally use annual agreements.
- Usage and license scope should be reviewed when the customer adds subsidiaries, clients, tenants, members, products, broader distribution rights, or materially higher sustained usage.
Indicative pricing. Final pricing is confirmed in writing before contracting.
10 · Credential + security handling
Treat API keys as secrets
- Use an account-specific key and record the correct owner, scope, limits, environment, creation date, and expiration internally.
- Do not store active keys in broadly shared strategy pages, decks, screenshots, tickets, reusable templates, or shared conversations.
- Deliver credentials through the approved private provisioning path rather than embedding them in public examples.
- Rotate a key immediately if it appears in a shared document or communication beyond the intended recipient.
YOUR_ACCOUNT_SPECIFIC_API_KEYSecurity reviews, service levels, dedicated infrastructure, and other nonstandard production commitments require an explicit production scope.
11 · Developer resources
Current links and documentation status
| Resource | Status | Link / guidance |
|---|---|---|
| API docs | Available | api.iamaware.us/v1/docs |
| Browser console | Available | Included in the documentation page. |
| Base URL | Available | api.iamaware.us/v1/ |
| OpenAPI download | Not published | Use the live documentation for the current schema. |
| Postman collection | Not published | Build against the documented REST endpoints. |
| SDKs | Not published | Use direct REST access. |
| Webhooks / push | Not standard | Delivery is pull-based. Push is not part of the standard integration. |
| Status page / uptime SLA | Not public | Production service levels are scoped commercially, per account. |
12 · Errors + implementation contract
Use the live docs for exact response and error objects
This page deliberately does not restate the status-code table or the error JSON schema. A copy here would drift out of step with the API, and you would find out the hard way. Build against the live documentation and the browser console, which reflect current behavior.
Treat pagination, enum values, nullability, field types, sorting, and retry guidance the same way: if it is not stated in the current API reference, do not infer it from this page.
13 · Product boundary
Signals stops at the government-action data layer
Signals does not include customer-specific business profiling, exposure scoring, company-specific financial or operational impact analysis, cross-functional consequence mapping, recommended response options, ranked Next Move, or enterprise case-management workflows unless those capabilities are purchased separately through Aware Platform or Enterprise.
Start with the live API
Use the docs and browser console for exact technical behavior, then use the 14-day evaluation to test Signals inside one real workflow.