Add 48 SDK modules and 4,627 endpoints to your Windsurf workflow. Create and operate any SaaS from your agent.
Sign up at tyga.run/signup (free tier, no credit card). Or use tAI chat to create your SaaS in 2 minutes.
Add this to your .windsurfrules:
# tyga.run SDK Integration See: https://tyga.run/llms.txt API Base: https://sdk.tyga.run API Key: YOUR_API_KEY ## Quick Reference - POST /saas/provision — Create full SaaS (record + API key + plan + community) - POST /auth/signup — Create user (auto-creates org, workspace, subscription) - POST /billing/subscriptions — Create subscription - POST /scheduling/bookings — Create booking - POST /crm/leads — Create CRM lead - POST /support/tickets — Create support ticket - POST /ecommerce/products — Create product - GET /docs — Interactive API docs (48 modules) All requests: -H "Authorization: Bearer YOUR_API_KEY" -H "Content-Type: application/json"
Windsurf reads this at session start and gains full SDK knowledge.
Ask Windsurf: "Create a scheduling SaaS called MyBookings"
curl -X POST https://sdk.tyga.run/saas/provision \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"saasId": "mybookings",
"name": "MyBookings",
"category": "scheduling",
"ownerEmail": "you@example.com"
}'
# Returns: apiKey, domain, subscription plan, community — all provisioned
# {
# "success": true,
# "saasId": "mybookings",
# "apiKey": "tc_live_mybo_...",
# "domain": "mybookings.tyga.run",
# "steps": ["saas-created", "subscription-plan", "community", "saas-json-file", "cache-cleared"]
# }
# Create a user
curl -X POST https://sdk.tyga.run/auth/signup \
-H "Authorization: Bearer $KEY" \
-d '{"email":"user@mybookings.com","password":"SecurePass123","firstName":"Jane"}'
# Create an event type
curl -X POST https://sdk.tyga.run/scheduling/event-types \
-H "Authorization: Bearer $KEY" \
-d '{"name":"30-Min Consultation","duration":30,"location":{"type":"video"}}'
# Create a booking
curl -X POST https://sdk.tyga.run/scheduling/bookings \
-H "Authorization: Bearer $KEY" \
-d '{"eventTypeId":"evt_...","customer":{"name":"John","email":"john@example.com"}}'
# Create a support ticket
curl -X POST https://sdk.tyga.run/support/tickets \
-H "Authorization: Bearer $KEY" \
-d '{"subject":"Booking issue","description":"Cannot reschedule my meeting"}'
# Check platform stats
curl https://sdk.tyga.run/health -H "Authorization: Bearer $KEY"
Every module is callable via REST. Your agent picks the modules it needs:
Identity: auth, apikeys, teams, saas Finance: billing, accounting, open-banking Sales: crm, contracts, recruitment Engagement: scheduling, channels, support, community, notifications, email, surveys Commerce: ecommerce, event-ticketing, marketplace Content: website, news-publishing, elearning, file-management AI: ai, analytics, gamification, widgets, datagrab Telecom: icuk, mvno, broadband, broadbandprovisioning, isp, ispreseller, hosting, domains Compliance: compliance, hmrc, companieshouse Infra: appdeploy, webhooks, map, postcode, project-management, tyga Verticals: esports, fitness
Your agent doesn't just call APIs — it runs autonomous business loops:
LOOP 1: Customer Onboarding Agent calls POST /auth/signup → user created Agent calls POST /billing/subscriptions → Stripe subscription active Agent calls POST /scheduling/event-types → booking page live → Customer can self-serve. Zero human touch. LOOP 2: Support Operations Customer submits ticket → POST /support/tickets Agent reads GET /support/tickets?status=open Agent responds via POST /support/ticket-messages Agent resolves via PATCH /support/tickets/:id → Support runs 24/7. Agent handles it. LOOP 3: Sales Pipeline Agent creates lead → POST /crm/leads Agent qualifies → PATCH /crm/leads/:id (BANT scoring) Agent converts → POST /crm/opportunities Agent tracks → GET /crm/pipelines → Pipeline managed by agents. You watch the dashboard.
llms.txt — Machine-readable API reference
API Docs — Interactive swagger UI for all 48 modules
Sign Up — Free tier, no credit card