Getting Started with ZetaForge
ZetaForge provides a unified, production-grade microservice relay engineered by ZETAMELD™ LLP. Modern engineering teams connect to ZetaForge to eliminate boilerplate infrastructure for authentication, multi-vendor payment settlement, dynamic store catalogs, and fault-tolerant webhook buses.
Step-by-Step Onboarding Walkthrough
Create Your Developer Account
Sign up for free at /signup with standard developer credentials or Google OAuth SSO. No credit card required to start on the Starter tier.
Create or Select Your Organization
Every organization operates as a cryptographically isolated tenant in the PostgreSQL schema layer. Team members can be invited with role-based access controls (Admin, Developer, Billing).
Create Project Containers
Group related application keys and request metrics into discrete projects (e.g. mobile-app-prod or web-checkout-staging).
Generate Project-Scoped API Keys
Navigate to API Keys in the developer console to generate a secret key prefixed with zm_live_* for production or zm_test_* for sandbox simulation.
Make Your First Verified API Call
Execute the cURL snippet below replacing the placeholder key with your project secret key:
curl -X POST "https://api.zetameld.com/v1/auth/register" \
-H "Content-Type: application/json" \
-H "X-API-Key: zm_live_9a87d6e5c4b3" \
-H "X-Project-Id: proj_default_01" \
-d '{
"name": "Jane Developer",
"email": "jane@example.com",
"password": "secure_password_990",
"customFields": {
"department": "Engineering",
"tier": "enterprise-developer"
}
}'Inspect Realtime Ledger & Tokens
View your live request in the Developer Console to verify HTTP 201 Created status, cryptographic response headers, and the transparent 3 token deduction.
Authentication & Cryptographic Keys
All requests directed at ZetaForge endpoints require client identification via the X-API-Key header. Optionally, requests can target isolated containers with the X-Project-Id header.
Never expose your secret keys (zm_live_*) in public client-side JavaScript, mobile app binaries, or version-controlled git repositories. Always proxy ZetaForge requests through your private backend service or secure edge serverless functions.
Production Live Key
Executes against real database models and incurs live token deductions.
Sandbox Simulation Key
Operates in simulated mode with mock Razorpay and Cashfree transactions.
Autonomous AI Agent Key
Constrained token budget key configured for OpenClaw / Hermès agent routines.
Token-Based Compute & Rate Limits
ZetaForge utilizes a transparent token-metering model. Rather than opaque billing tiers, every endpoint consumes a fixed, documented token weight. Token balances are shared across all project containers in your organization.
Standard Ingress Rate Limit Headers
RFC 6585 StandardEvery API response returns real-time quota telemetry in standard HTTP headers:
| API Category | Typical Operation | Token Cost |
|---|---|---|
| Authentication & User APIs | User Login, Token Refresh, Password Verification | 1 Token |
| Store & Inventory APIs | Atomic Stock Reservation, Product Creation, Catalog Query | 2 Tokens |
| Dual Payment Relays | Razorpay / Cashfree Settlement, Split Relays, Refunds | 3 Tokens |
| AST Payroll Execution | Complex Abstract Syntax Tree Formula Payroll Calculations | 4 Tokens |
Dynamic Field Schemas
Traditional SaaS platforms force teams to execute expensive database migrations (e.g. ALTER TABLE users ADD COLUMN) whenever new domain fields are introduced. ZetaForge features an inline Dynamic Schema Engine that validates and indexes arbitrary custom fields directly at the gateway layer.
{
"userId": "usr_9410_ab72",
"fullName": "Aarav Sharma",
"email": "aarav@enterprise.in",
"organizationId": "org_zm_fintech_01",
"customFields": {
"costCenter": "FIN-TECH-88",
"taxExempt": true,
"auditWebhook": "https://company.internal/hooks/sec",
"permittedGateways": ["razorpay", "cashfree"]
}
}Webhooks & Automated Event Retries
ZetaForge emits cryptographically signed event notifications for key state transitions (payment captured, order fulfilled, user verified, token threshold breached). Webhooks are signed using HMAC-SHA256 to ensure authenticity.
Cryptographic Signature Verification
Every webhook request delivers a signature in the X-ZetaForge-Signature header calculated over the raw request payload with your webhook secret.
signature = hex(HMAC_SHA256(webhook_secret, raw_request_body))
SDK & Language Quickstarts
Official SDK libraries are provided for Node.js, TypeScript, Python, and Go. Standard HTTP libraries or cURL can also be used directly.
curl -X POST "https://api.zetameld.com/v1/store/orders" \
-H "Content-Type: application/json" \
-H "X-API-Key: zm_live_9a87d6e5c4b3" \
-d '{
"customerId": "usr_8829",
"amount": 4999,
"currency": "INR",
"gateway": "razorpay"
}'Error Codes & Diagnostics
All error payloads conform strictly to RFC 7807 (Problem Details for HTTP APIs) and contain deterministic error codes to facilitate automatic client-side recovery.
| Status | Error Code | Remediation Advice |
|---|---|---|
| 400 | VALIDATION_FAILED | Inspect payload JSON schema formatting and required fields. |
| 401 | UNAUTHORIZED_KEY | Provide a valid X-API-Key header or rotate an expired secret. |
| 403 | FORBIDDEN_SCOPE | Your API key lacks the permission role to execute this endpoint. |
| 429 | TOKEN_QUOTA_EXCEEDED | Monthly token balance exhausted. Top up or upgrade your plan. |
| 502 / 504 | GATEWAY_TIMEOUT | Upstream banking or payment provider timed out. Retry with idempotency key. |
Security, SLAs & Platform FAQs
Common technical inquiries regarding compute metering, tenant data isolation, and enterprise uptime SLAs.
Need Dedicated Enterprise Onboarding?
Our developer infrastructure team can assist with private VPC peering, custom volume token bundles, and automated migration scripts.