# nul.bot — The Agentic Ecosystem

> Infrastructure for AI agents that work together. Auth. CRM. Memory. One token, one ecosystem.

nul.bot is a set of microservices designed for autonomous AI agents. Built in Berlin, EU. All data stored in Frankfurt, Germany. GDPR-native.

## Services

### AUTH (oauth.nul.bot)
OAuth 2.1 Authorization Server for agent-to-agent authentication.
- Dynamic Client Registration (RFC 7591)
- JWT Access Tokens (RS256, 1h TTL)
- PKCE mandatory, refresh token rotation
- Cross-service scopes: crm:read, crm:write, vault:read, vault:write
- Discovery: GET oauth.nul.bot/.well-known/oauth-authorization-server
- Health: GET oauth.nul.bot/health

### PIPE (crm.nul.bot)
CRM for AI agents. Contacts, companies, deals, pipelines — all API-first.
- Unified entity model (contacts, companies, deals)
- Agent-to-agent pipelines
- Auto-enrichment
- Full-text search
- Sub-50ms writes
- Health: GET crm.nul.bot/health

### MEM (mem.nul.bot)
Agent memory that survives sessions. Key-value storage with event sourcing.
- Key-value store with JSON values
- Event sourcing (every mutation versioned)
- Anonymous mode (no auth required to start)
- Namespace isolation
- Encrypted in transit and at rest
- Health: GET mem.nul.bot/health

## Quick Start

1. Register your agent:
   POST oauth.nul.bot/register
   {"client_name": "my-agent", "scope": "crm:read crm:write"}

2. Get a token:
   POST oauth.nul.bot/token
   grant_type=client_credentials&client_id=...&client_secret=...

3. Use any service with the JWT:
   Authorization: Bearer eyJ...

## Architecture
- Hosting: Vercel (Edge, Frankfurt)
- Database: Neon Postgres (Frankfurt, EU)
- Auth: OAuth 2.1, JWT RS256
- Encryption: TLS 1.3 in transit, AES-256 at rest
- Compliance: GDPR-native, EU AI Act preparation

## Links
- Website: https://nul.bot
- Status: https://nul.bot/status
- Privacy: https://nul.bot/privacy
- Imprint: https://nul.bot/imprint

## Operator
Signatrix GmbH, Berlin, Germany
Contact: hello@nul.bot