warp-drive.io valid
The Manual
Boldly Read What No Dev Has Read Before
- Authority
- 45 reach 0 · trust 5 · quality 25 · freshness 15
- Tier
- listed
- llms.txt
- https://canary.warp-drive.io/llms.txt
- llms-full.txt
- https://canary.warp-drive.io/llms-full.txt
- Sections
- 1
- Links
- 722
- Size
- 172111 bytes
- Country
- — Publisher location unknown; CDN address excluded
- Country evidence
- No published address evidence collected yet
- For agents
- Documentation: developer or product docs worth reading, nothing to call
- First seen
- 2026-10-23T22:03:41.561Z
- Last checked
- 2026-10-23T22:03:42.892Z
- Badge
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-23T22:03:41.568Z. Cached copy · Source on warp-drive.io
# The Manual
> Boldly Read What No Dev Has Read Before
Comprehensive Documentation for Engineers Aiming for the Stars 💫
Guides for legacy setups and API reference for `@warp-drive/legacy`, `@ember-data/adapter`, `@ember-data/active-record`, `@ember-data/debug`, `@ember-data/legacy-compat`, `@ember-data/model`, `@ember-data/json-api`, `@ember-data/store`, `@ember-data/graph`, `@ember-data/request`, `@ember-data/request-utils`, `@ember-data/rest`, `@ember-data/serializer`, `@ember-data/tracking`, `@warp-drive/core-types`, `@warp-drive/build-config`, `@warp-drive/schema-record` are indexed separately in https://canary.warp-drive.io/llms-legacy.txt, with full text in https://canary.warp-drive.io/llms-legacy-full.txt.
## Table of Contents
### Installation
- [Instructions](https://canary.warp-drive.io/guides/installation.md): Install @warp-drive/core and @warp-drive/json-api with exact pinned versions, then add the reactivity package and install import for Ember, React, or TC39 Signals.
- [UNPKG](https://canary.warp-drive.io/guides/installation/unpkg.md): Load prebuilt ESM builds of WarpDrive packages from UNPKG and pick the unpkg, unpkg-dev, unpkg-deprecated, or unpkg-dev-deprecated export condition you need.
### Configuration
- [Setup](https://canary.warp-drive.io/guides/configuration.md): Set up WarpDrive's babel build plugin with compatWith and create a store with useRecommendedStore or useLegacyStore, the two steps required before making any request.
- [Setup - Advanced](https://canary.warp-drive.io/guides/configuration/advanced.md): Build a Store class by hand, adding RequestManager, SchemaService, JSONAPICache, instantiateRecord, and DefaultCachePolicy step by step, with Ember Model and migration variants.
- [Setup - React](https://canary.warp-drive.io/guides/configuration/react.md): Provide your WarpDrive store to React components with StoreProvider, read it with useStore, and know when a component re-renders.
### Tutorials
- [Overview](https://canary.warp-drive.io/guides/tutorials.md): Learn WarpDrive by building apps step by step, starting with the data layer of a TodoMVC app in Ember, written one request at a time.
#### TodoMVC
- [0. Setup](https://canary.warp-drive.io/guides/tutorials/todomvc.md): Build the data layer of a TodoMVC app with WarpDrive and Ember. Create the starter with npx @warp-drive/tutorials, run it, and see where you'll write WarpDrive code.
- [1. First request](https://canary.warp-drive.io/guides/tutorials/todomvc/first-request.md): Request the todos with store.request, then render the Future it returns with a <Request> block.
- [2. Why that worked](https://canary.warp-drive.io/guides/tutorials/todomvc/why-that-worked.md): The four ideas WarpDrive is built on: requests instead of models, one path for every request, one cached copy of each thing, and read-only records.
- [3. Request builders](https://canary.warp-drive.io/guides/tutorials/todomvc/request-builders.md): Write each request once, as a builder, and
…Machine-readable: GET /v1/resolve?q=warp-drive.io · GET /v1/domain/warp-drive.io · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage warp-drive.io, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for warp-drive.io:
1. POST https://agentwebmap.com/v1/sites/warp-drive.io/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://warp-drive.io/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/warp-drive.io/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/warp-drive.io).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.