Cosantoir
DownloadAccess Portal

[ Resources command center ]

API, pricing, downloads, and shop. Unified.

Builders, buyers, operators, and support teams get one place to move into docs, install paths, merch, pricing, status, and launch readiness without losing momentum.

Open API docsDownload appsShop merch
01

Developers

API Reference

Endpoints, schemas, authentication, and response contracts for platform integrations.
REST + SDK
02

Workspace

Developer portal

Manage keys, quickstarts, docs, and integration validation from the authenticated portal.
Keys + usage
03

Install

Downloads

Route desktop, mobile, browser, and extension clients into the right install path.
All surfaces
04

Storefront

Shop merch

Open the public shop for plans, merch capsule items, and rollout buying paths.
Plans + merch

[ Immersive resource story ]

Scroll from API intent into launch readiness.

Resources now has a real story arc: builders enter through docs, buyers keep pricing and shop close, and operators leave with install, support, and status routes.

Builder pathAPI + SDKBuyer pathPricing + shopInstall pathDownloadsLaunch pathStatus + support
Resource 01API surface

Reference, schemas, SDKs, and portal access form the technical camera angle.

REST + SDK
Resource 02Install surface

Download routes pull desktop, mobile, browser, and extension into one launch path.

12 routes
Resource 03Shop surface

Pricing and merch stay discoverable without replacing the API and support paths.

Plans + merch
01
Builder entry

Resources starts with the person trying to ship or integrate.

API docs, SDKs, CLI references, and developer portal access stay visible before the visitor loses the build context.

02
Commercial bridge

Pricing, download, and shop remain part of the same resource story.

A buyer can compare plans, install apps, or open merch without the Resources page becoming another generic blog index.

03
Launch readiness

Status, support, and documentation complete the operating loop.

The page lands on the launch details teams need after a decision: uptime, support route, docs depth, and install confidence.