Changelog
All notable changes to Treeship.v0.1.0 (2026-02-23)
Initial Release The first public release of Treeship, providing cryptographic attestations for AI agents.Features
- Ed25519 Attestations: Create cryptographically signed records of AI agent actions
- Independent Verification: Verify any attestation without trusting Treeship servers
- Public Verification Pages: Shareable URLs for each attestation at
treeship.dev/verify/{agent}/{id} - Agent Feeds: View all attestations for an agent at
treeship.dev/verify/{agent} - Self-Service API Keys: Email verification flow for API key generation
- Rate Limiting: 1000 attestations/day per API key
SDKs
- Python SDK (
treeship-sdk): Full-featured SDK with async support - Node.js CLI (
treeship-cli): Command-line tool for attestations and verification
API Endpoints
| Endpoint | Description |
|---|---|
POST /v1/attest | Create attestation |
GET /v1/verify/:id | Verify attestation |
GET /v1/agent/:slug | Get agent feed |
GET /v1/pubkey | Get public key |
POST /v1/keys/request | Request verification code |
POST /v1/keys/verify | Verify and get API key |
Documentation
- Quickstart guides for Python and Node.js
- API reference documentation
- Concepts: Attestations, Verification, Trust Model
- Guides: CLI Reference, Self-hosting
Roadmap
Coming Soon
- ZK Proofs: Prove properties about agent actions without revealing data
- Go SDK: Native Go client library
- Rust SDK: Native Rust client library
- Webhooks: Real-time notifications for attestation events
- Custom Signing Keys: Bring your own Ed25519 keys per agent
- Team Management: Multiple users per organization
- Usage Dashboard: Analytics and monitoring
Future
- Escrow Integration: Conditional payments based on verified attestations
- Custom ZK Circuits: Define your own proof types
- On-chain Anchoring: Optional blockchain timestamps
Versioning
Treeship follows Semantic Versioning:- Major (1.x.x): Breaking API changes
- Minor (x.1.x): New features, backwards compatible
- Patch (x.x.1): Bug fixes, backwards compatible
/v1/. Breaking changes will use /v2/, etc.