OpenAI compatible API · Attested · Public status

AkashML

Explore AkashML models on TrustedRouter with current routes, token pricing, policy sources, privacy posture, regional availability, and API support.

Verify gateway

Onebase URL to migrate

100sof models and routes

0prompt or output logs. Always.

AkashMLakashml

No provider claim

All providers

These privacy labels describe AkashML, the upstream model provider. Confidential requires all three: verified provider compute, end-to-end encryption and explicit zero data retention. Account and billing metadata are outside the content-retention claim.

Provider	AkashML
API operator country	Not verified Legal home of the API operator, not an inference-location guarantee.
Headquarters	Not verified
Routing status	Active
Provider website	https://akashml.com/
Models	7 public models
Credits routes	7
Zero data retention	not claimed
Verified confidential inference	Not verified
Policy note	No contractual zero-retention, confidential-compute, or E2EE claim is tracked for TrustedRouter's AkashML account. This route is Standard. Policy source

Inference locations

Provider API declarations are also available on each model's endpoint API. Direct chat and Responses replies separate advertised availability from serving location in usage.inference_location; the actual serving region remains unknown when not reported.

Where the upstream GPUs execute the model, not the provider's headquarters, API ingress, or data storage. ZDR and confidential inference do not by themselves restrict geography.

Declared countries or regions: Not verified
No inference-location declaration has been verified for this provider.
Can locations change?: Not verified. Do not assume that the serving location is fixed.
Provider region pinning: Not verified.
Pinning through TrustedRouter: No verified provider-specific location pin documented here.
Infrastructure declaration: Inference location not verified; no country-specific residency commitment.
Evidence: Not yet reviewed.

Provider selection alone is not a region pin. TrustedRouter's US provider filter selects company jurisdiction, not GPU location. A regional gateway hostname does not pin a downstream GPU. For a binding residency requirement, confirm the model, region, failover scope and enforced controls before sending sensitive data.

Measured performance

20 samples

Continuously sampled across AkashML's routed models: p50 TTFT, effective throughput, and success rate. Effective throughput uses provider-reported output tokens over complete request time. Unsupported route and probe-configuration rows are separated from provider downtime. No prompt or output content stored.

p50 TTFT	1418 ms
Effective throughput	211 tok/s n=3
Uptime	90.00%

Model	p50 TTFT	Effective throughput	Uptime	Config excluded	Availability samples
openai/gpt-oss-20b	667 ms	—	100.00%	—	2
openai/gpt-oss-120b	934 ms	—	100.00%	—	2
z-ai/glm-5.3	1145 ms	211 tok/s n=2	100.00%	—	1
meta-llama/llama-3.3-70b-instruct	1237 ms	—	75.00%	—	4
qwen/qwen3.8-27b	1418 ms	—	100.00%	—	4
moonshotai/kimi-k3	1958 ms	100 tok/s n=1	85.71%	—	7

AkashML performance history · Full provider & model leaderboard.

Provider models

Models served by AkashML.

Each row links to pricing, provider, benchmark, and API pages for the model.

Model	AI IQ	Context	Input	Cached input	Output
`meta-llama/llama-3.3-70b-instruct` Meta: Llama 3.3 70B Instruct benchmarks	—	131,072	$0.211/1M	$0.1055/1M	$0.5486/1M
`moonshotai/kimi-k3` MoonshotAI: Kimi K3	IQ 127#20	1,048,576	$3.165/1M	$0.3165/1M	$15.825/1M
`openai/gpt-oss-120b` OpenAI: gpt-oss-120b	IQ 98#126	131,072	$0.039035/1M	$0.039035/1M	$0.197285/1M
`openai/gpt-oss-20b` OpenAI: gpt-oss-20b	IQ 94#140	131,072	$0.0211/1M	Not published	$0.1055/1M
`qwen/qwen3.6-35b-a3b` Qwen: Qwen3.6 35B A3B	IQ 104#100	262,144	$0.1055/1M	$0.05275/1M	$0.9495/1M
`qwen/qwen3.8-27b` Qwen: Qwen3.8 27B	IQ 116#50	65,536	$0.237375/1M	$0.05275/1M	$2.0889/1M
`z-ai/glm-5.3` Z.ai: GLM 5.3	IQ 125#24	1,048,576	$1.23435/1M	$0.2743/1M	$4.1778/1M

Questions

Does AkashML have zero data retention?

TrustedRouter does not currently mark AkashML as provider-level zero data retention. Use trustedrouter/zdr or provider.min_privacy=zdr to select a different eligible route, and review the linked policy source for changes.

Is AkashML end-to-end encrypted?

TrustedRouter does not currently mark AkashML as end-to-end encrypted at the provider boundary. The TrustedRouter gateway is still attested, but the selected provider normally receives the request in order to run the model. Use trustedrouter/e2e for the stronger route requirement.

Which AkashML models are available through TrustedRouter?

This page currently lists 7 public AkashML models, with live pricing, route count, context length, measured performance when available, and links to each model's provider and benchmark pages.