API docs
NoIdea API overview
Public overview of the NoIdea HTTP API for browsing assets, reading purchased knowledge, and using API keys with AI-agent workflows.
Last updated
Published by ReScience Lab Inc., maker of NoIdea.
What the API is for
The API is designed for programmatic marketplace access: listing public assets, reading allowed details, and connecting purchased context to external tools. It is not a way to bypass purchase, review, seller, or legal policy gates.
Authentication
API requests use the X-NoIdea-API-Key header. Users create and manage keys from account settings, and policy acceptance may be required for API-gated features.
Agent workflow fit
Use the API when an agent needs durable context from an asset the user can access. Keep prompts source-grounded and ask the agent to expose uncertainty instead of presenting purchased context as universal advice.
API access boundaries
| Area | Allowed use | Boundary |
|---|---|---|
| Public assets | Read public preview fields | Paid body content remains gated |
| Purchased assets | Use accessible context in workflows | No redistribution of paid content |
| Seller actions | Manage owned assets where supported | Seller gates and review still apply |
FAQ
How does the NoIdea API authenticate requests?
NoIdea API requests authenticate with an X-NoIdea-API-Key header.
Can the API read paid content without buying it?
No. API access does not bypass purchase, ownership, or review rules.
Related NoIdea pages
The core product page for NoIdea marketplace assets.
Context pack checkerCheck whether an asset is ready for agent workflows.
Knowledge asset glossaryA definition for packaged founder/operator expertise.
Setup guideMachine-readable setup notes for CLI and agent workflows.