01Overview
Ascent’s developer assets are licensed commercially and by vehicle — hosted API access, internal SDK use, embedded distribution and white-label/self-hosted resale carry different rights, deployment scope and support. This page summarises the framework; the binding terms live in your Order and the applicable addenda. For access, contact hello@ascent.dev.
02Asset classification
| Asset | Legal vehicle | Default grant |
|---|---|---|
| Hosted API | API Terms + Order | Non-exclusive, non-transferable access for authorised applications within quotas |
| SDK / core package | Commercial SDK EULA | Internal development & deployment for licensed applications |
| MCP server / assistant skill | Integration addendum | Internal or embedded use with named products/clients |
| Widgets | Redistributable component licence | Object-code embedding in licensed applications |
| Admin cockpit | Operator / white-label addendum | Operate licensed deployments; no standalone resale |
| Self-hosted engine | Enterprise source/object licence + support | Named deployment/environment and authorised affiliates |
| Examples, schemas & types | MIT / Apache-2.0 where separable | Broad reuse without rights to the proprietary engine |
03Licence tiers
| Tier | Rights | Model |
|---|---|---|
| Developer evaluation | Local, non-production evaluation; no customer data or resale | Free / 30 days; click-through |
| Internal production | One legal entity; named applications & environments | Annual minimum + usage |
| Embedded OEM | Distribute Ascent-powered functionality inside a named product; no standalone access | Annual platform fee + active-customer/site royalty |
| Agency managed service | Use for client sites while you remain operator | Portfolio/site fee; no source redistribution |
| White-label | Brand removal & client-facing resale under an approved product | Higher annual minimum + deployment, usage & support |
| Enterprise self-hosted | Run an approved version in your controlled environment | Per deployment/region + annual maintenance |
04Core grant
Subject to the Order and payment, we grant you a limited, non-exclusive, non-transferable, non-sublicensable licence during the term to install, execute and reproduce the licensed assets solely for the named applications, environments, sites, affiliates and purposes in the Order. Embedded and white-label rights exist only if expressly purchased. Contractors may use the assets solely for you, under confidentiality, and must cease on completion.
05Restrictions
- No standalone redistribution, public package-registry publication, or making source available to third parties.
- No service bureau, timesharing, competing SEO platform or resale except within purchased agency/OEM/white-label rights.
- No circumvention of entitlement, metering, signature, rate-limit or usage control.
- No reverse engineering except to the limited extent mandatory law cannot waive.
- No use of the assets, outputs or non-public documentation to train or benchmark a competing model or product.
- No removal of proprietary notices except where white-label rights expressly permit it, and no use of Ascent trademarks in a product name without written approval.
06API terms
- Keys are confidential, scoped to the licensed application, and may not be placed in public clients.
- Quotas, concurrency, rate limits and operation definitions are set in your Order and machine-readable headers.
- We may make backward-compatible changes; breaking changes get a versioned endpoint and a proposed 12-month deprecation period.
- You control submitted data and receive output rights per the main Terms; providers and open-source components retain their rights.
- Uptime, support hours, maintenance and service credits are set in an SLA for paid enterprise plans.
07MCP, skills & agents
Each exposed tool, permission and data destination is defined. The host application must obtain authority for connected sites and display meaningful confirmation before high-impact writes. You may not represent the agent as infallible or conceal automatic publishing. Tool calls count toward usage. Distribution through an AI-client marketplace requires a prior security review and a specific channel addendum.
08White-label & agency
You are the customer-facing provider and must supply compliant end-user terms and a privacy notice. We remain owner of the engine — white-label is brand permission, not assignment. Sublicensing is permitted only to end customers as embedded functionality. You handle first-line support; we handle escalations under purchased support. Customer/site counts and usage are reported monthly and auditable annually.
09Pricing architecture
| Right | Commercial model |
|---|---|
| Internal SDK/API production | Annual minimum + usage |
| Agency managed service | Annual minimum + sites/usage |
| Embedded OEM | Annual platform fee + active-deployment royalty |
| White-label | Annual minimum + implementation, support & usage |
| Enterprise self-hosted | Per deployment/region + annual maintenance |
These describe rights/risk segmentation, not list prices — commercial terms scale with deployment scope, distribution rights and support. We share pricing on request; source access / escrow is quoted separately. Contact hello@ascent.dev.
10The contract stack
- Master Subscription/Services Agreement or Terms of Service.
- Order Form defining assets, applications, sites, environments, regions, usage and fees.
- Developer/API Addendum with versioning, quotas and prohibited uses.
- Data Processing Addendum and subprocessor list.
- Security exhibit and SLA for enterprise.
- OEM/white-label addendum where distribution or resale is permitted, plus open-source and third-party notices.
Ready to build on Ascent? Explore the developer portal or request a licence →