Home / Compute
Declaw
docs.declaw.ai/platform/billingContainer and VM sandboxcompute/declawJSONcomparereport an errorprovider JSON
- Free allowance
- $100 of sandbox compute credit and a separate $200 of guardrails credit, both one-time and never refilled; compute meters every 30 seconds at $0.0504 a vCPU-hour
- Verdict
- caveatusable, with a named limit or an unprobed read path
- Cost
- free tier
- Identity
- email?placeholder, not evidence; card unknown, phone unknown
- Binding limit
- request-rate$0.0504 a vCPU-hour, $0.0162 a GB-hour of memory and $0.110 a GB-month of disk
- Evidence
- documented6 sources; a first-party page was read and the sentence quoted
- Freshness
- stale on 2026-12-05checked 2026-11-04 (live); stale on 2026-12-05
| Free tier | $100 of sandbox compute credit and a separate $200 of guardrails credit, both one-time and never refilled; compute meters every 30 seconds at $0.0504 a vCPU-hour unit mixed; metered on wall-clock |
|---|
| Price | none stated |
|---|
| Limits | - request-rate (binding) $0.0504 a vCPU-hour, $0.0162 a GB-hour of memory and $0.110 a GB-month of disk source
- retention-clamped metering ticks every 30 seconds and a delayed tick is capped at 90 seconds of billable time, so a stop is noticed within 90 seconds source
- per-object-cap the two grants are one-time: $100 for sandbox compute and $200 for guardrails, never refilled source
not stated |
|---|
| Identity | email (placeholder) not published |
|---|
| Egress | not published: the archived billing and plans pages state no traffic allowance or per-GB overage; the plans table caps egress connections per sandbox at 50 on Free and 200 on Pro |
|---|
| Per-object cap | not stated |
|---|
| Retention | not stated |
|---|
| Interface | rest, cli REST API with an X-API-Key header, the declaw CLI, and Python, TypeScript and Go SDKs (archived docs index of 2026-10-13) |
|---|
| Reliability | unverified: docs.declaw.ai answered DNS status 3 (NXDOMAIN) on 2026-11-04 and declaw.ai has no address record, so the billing page is readable only in archived copies of 2026-05-26 and 2026-10-13 |
|---|
| Evidence note | documented the billing page was read on 2026-10-22 and states both grants, the microdollar metering and the 30-second tick with its 90-second cap. The record carried only the $100; the $200 is a second wallet with its own meter |
|---|
| Parsed numbers | |
|---|
Evidence 6
More fields 7
| keep rate | 1.0 |
|---|
| billing model | unclassified |
|---|
| shape | {"vcpu": 2,"ram": 4,"disk": 10,"gpu_class": null,"gpu_count": null,"note": "the page's own worked example: 2 vCPU, 4 GB and 10 GB for an hour costs 100,800 + 64,800 + 1,526 microdollars"} |
|---|
| session cap | {"wall_clock_min": null,"idle_reap_s": null,"restart_required": false,"note": "metered every 30 seconds against provisioned resources; a lagging tick bills at most 90 seconds"} |
|---|
| free tier kind | one-time-credit |
|---|
| burst x | 1.0 |
|---|
| ps | {"gib": 10,"price": "$0.110 a GB-month of overlay disk","durability": "overlay disk","on_stop": true,"on_destroy": false,"retention": "until deleted"} |
|---|
Unknown values 7
- chaining: a source was read and is silent on this field
- egress metered: egress metering was not published
- limits note: a source was read and is silent on this field
- per object cap stated: a source was read and is silent on this field
- retention notes: the field may be stated in a source that was not read
- retention stated: a source was read and is silent on this field
- tooling: a source was read and is silent on this field