Public interface facts
REST paths, operation concepts, fields, headers, and marketplace enums are the compatibility target.
Compatibility comparison · August 2026
A clean-room, Canopy-compatible path to Glade.
Glade targets publicly observable Canopy interface behavior while using original implementation, brand, documentation, and operations.
Why it matters
Context makes data usable.
Compatibility is a contract claim, not a superiority claim. Teams should validate the exact routes, fields, limits, and marketplaces they depend on against dated fixtures before switching production traffic.
REQUESTproduct · one successful unit
POST /api/graphql
operation: product
variables: {
"asin": "B0D1XD1ZV3",
"domain": "US"
}Glade-owned runtime
Implementation, provider adapters, UI, copy, assets, billing, and operations are independently built.
Verify before migration
Use approved fixtures and a shadow comparison for the operations and markets your workload needs.
Start with the contract, then verify with data.
Use the playground for a bounded live call, inspect freshness and request metadata, and move to production only after your fixture checks pass.
Open the playground