Usage
Sanvex follows one pattern everywhere: resolve a driver, pick a resource, call an action.Basic pattern
Check configuration
Before calling a driver, verify credentials are stored:Multi-tenancy
Scope credentials and driver instances to an owner:Local database access
Some drivers cache entities insv_entities. Access them via db():
driver and entity_type but not by owner in the base implementation.
Webhooks
Sanvex registersPOST /sanvex/webhook for incoming webhook payloads. Drivers implement handleWebhook() and verifySignature().
Agent integration
Expose Sanvex to AI agents through:- Laravel AI —
SanvexAitools for Laravel AI SDK agents - MCP — stdio or HTTP SSE server for MCP clients
Discover available operations
sanvex_list_operations tool after starting php artisan sanvex:mcp-stdio.
Next steps
- Integration guide — install → connect → verify checklist
- Drivers — per-driver setup and API surface
- Authentication — token and OAuth setup
