Api.Airforce
Named model routes currently listed at zero price.
https://api.airforce/v1Models mentioned
The offer covers a dynamic catalog, provider-selected route, or model class without stable model IDs in this snapshot.
Equivalent paid value
How this was valued: Documented free-plan envelope of 1 request/minute and 1,000 requests/day multiplied by the 4,096-token per-request completion cap that the live catalog documents for every free-tier chat model, priced at Api.Airforce's own paid per-token USD rates (customer_price_table, micro-USD, snapshot 2026-08-22). The headline assigns the shared request pool to rnj-1, the most expensive chat model carrying the catalog's free-tier marker (tier "free", 51 models); model rows are alternative maxima for the same shared pool and are not additive. Assumes uninterrupted saturation with no latency, concurrency, availability, or fair-use loss, and counts completion tokens only because no per-request input ceiling is documented. The provider's confirmed but unpublished per-model daily token cap can only reduce the realizable value, so the figures are strict upper bounds. Free-tier markers in the rotating catalog are volatile, and authenticated runtime verification of premium-looking free-tier entries such as rnj-1 and mistral-large-2512 has not been performed.
Limits and terms
- Requests Per Minute
- 1
- Requests Per Day
- 1,000
- Per Model Daily Token Cap
- Yes
- Per Model Daily Token Cap Amount
- unpublished
What happens to your prompts?
Content can be retained for safety without a fixed TTL, while training and upstream handling are not fully documented.
- Plan Scope
- Api.Airforce website, dashboard, and inference gateway; downstream model-provider policies also apply.
- Prompt Retention
- Submitted content is retained as needed for abuse, fraud, illegal-activity detection, and service safety, but no fixed content-retention period is published.
- Response Retention
- Responses may be processed by third-party model providers; a gateway-specific output-retention period is not documented.
- Ordinary Logging
- Request counts, IP addresses, model usage, request logs, subscription data, and authentication information are collected for operations, analytics, security, rate limits, abuse prevention, and improvement.
- Model Training
- not documented
- Product Improvement
- Analytics and request logs may be used to improve and maintain the platform; whether prompt content itself is used for model or product improvement is not clearly stated.
- Human Or Operator Access
- Content can be processed for abuse, fraud, illegal-activity detection, and safety; the policy does not define operator roles or access limitations.
- Subprocessors And Routing
- Requests and outputs may be handled by changing third-party model providers under their own terms and policies.
- Deletion Controls
- Closing an account disables access and releases identifiers but is described as a reversible soft deletion. EU/EEA and equivalent-region users may request erasure, subject to legal-retention exceptions.
- Caveat
- The policy acknowledges content retention without a duration and does not publish a no-training commitment. Do not infer privacy from the service's proxy role.
Governing documents
- Terms Of Service
- https://api.airforce/terms/
- Privacy Policy
- https://api.airforce/privacy/
Eligibility
- Account Required
- Yes
- Payment Method Required
- No