Python integration
Use the public REST API for application code. Use Hosted MCP for coding agents. The Python package named snipara is not currently published on PyPI, so this page does not provide an SDK installation command or advertise unpublished extras.
Primary path
For product integration: use API / SDK
Production Python integrations should follow the versioned REST contract in the public API reference.
Supported paths
| Need | Supported surface | Install |
|---|---|---|
| Python application or backend | REST API | Your normal HTTP client |
| AI coding agent | Hosted MCP | No local Python package required |
| Local stdio compatibility or client-package development | Published snipara-mcp package | pip install snipara-mcp |
Private preview boundary
The monorepo contains preview SDK source, but repository source is not a distribution contract. Do not depend on snipara, snipara[watch], snipara[runtime], or snipara[all] until a PyPI release and pack smoke test are published.
Authentication
Keep API keys in an environment-backed secret store. Never paste a real key into source, examples, or a committed configuration file. Send the authentication header documented by the endpoint you are calling and scope the request to the authenticated project.
Choose the next reference
- REST API reference for application requests and responses.
- Authentication guide for supported key and OAuth flows.
- create-snipara for agent onboarding.
- MCP tools for the agent-facing contract.