> ## Documentation Index > Fetch the complete documentation index at: https://docs.echozero.app/llms.txt > Use this file to discover all available pages before exploring further. # Register as a developer > Creates a developer-type API key with profile. Returns raw key and secret once. If already registered, returns 409. `payoutAddress` is optional — agent fee claims credit the Echo Zero in-app wallet. ## OpenAPI ````yaml https://mcp.echozero.app/api/docs-json post /api/developers/register openapi: 3.0.0 info: title: EchoZero MCP API description: >- EchoZero MCP Server - Developer API for agent management, trading, marketplace, and AI chat. **Rate Limiting:** All endpoints enforce per-API-key rate limits. Tiers: free (60 req/min), standard (300 req/min), premium (1000 req/min). Every response includes `X-RateLimit-Limit`, `X-RateLimit-Remaining`, `X-RateLimit-Reset` headers. Exceeding the limit returns `429 Too Many Requests` with a `Retry-After` header. version: '1.0' contact: {} servers: - url: https://mcp.echozero.app description: Production security: [] tags: - name: MCP Protocol description: >- Model Context Protocol (Streamable HTTP): `/mcp`, `/mcp/sse` — not under `/api`; same API key as REST - name: Health description: Server health check - name: API Keys description: API key generation, listing, and revocation - name: User description: >- User profile, sessions, social, onboarding, internal agent subscriptions, and bot activations (v1: /v1/users/me) - name: Token description: Token data and trending - name: Trade description: Trade execution and history - name: Strategy description: Strategy (trading bot) configuration and control - name: Agent description: Agent registration and management - name: AI description: AI chat, intent, and insights - name: Wallet description: Wallet operations, deposits, and withdrawals - name: Notification description: Notification management and settings - name: Auth description: >- Public authentication: signup / login lookup, code verification, Google OAuth, refresh, and sign-out. Returns `accessToken` / `refreshToken` in the JSON body. - name: OAuth description: >- OAuth 2.1 authorization-code + PKCE for AI assistant clients: `/oauth/authorize`, `/oauth/token`, `/oauth/introspect`, `/status`. - name: Activity description: User trade activity list and search - name: Feed description: Social activity feed timeline - name: Earn description: Leaderboard, rewards, and referrals - name: Statics description: Countries, languages, and static data - name: Misc description: File uploads and utility endpoints - name: Developer description: Developer registration and profile - name: Developer dashboard description: >- Per-agent dashboard: subscribers (anonymized), performance detail, signal history (v1) - name: Developer Agent description: Developer agent listings and management - name: Developer Agents (Marketplace) description: Public browse, search, and subscribe to external developer-listed agents - name: Admin description: Admin-only endpoints for review, approval, and platform management - name: Webhooks description: >- Inbound provider webhooks (no API key). Telegram signal-bot uses `X-Telegram-Bot-Api-Secret-Token` when configured. paths: /api/developers/register: post: tags: - Developer summary: Register as a developer description: >- Creates a developer-type API key with profile. Returns raw key and secret once. If already registered, returns 409. `payoutAddress` is optional — agent fee claims credit the Echo Zero in-app wallet. operationId: DeveloperController_register parameters: - name: x-signature in: header required: false description: >- HMAC-SHA256 signature: HMAC-SHA256(secretKey, timestamp + METHOD + path + body). Optional -- when omitted, HMAC verification is skipped. schema: type: string - name: x-timestamp in: header required: false description: >- Request timestamp in epoch milliseconds. Required when x-signature is provided. Rejected if drift exceeds 5 minutes. schema: type: string requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/RegisterDeveloperDto' examples: minimal: summary: >- Developer key only (payout optional; claims use Echo Zero wallet) value: name: Acme Dev fullAllFields: summary: With developer profile value: name: Acme Trading payoutAddress: 9WzDXwBbmkg8ZTbNMqUxvQRAyrZzDsGYdLVL9zYtAWWM developerProfile: companyName: Acme Inc. website: https://acme.example contactEmail: dev@acme.example responses: '201': description: Developer registered. Raw key and secret returned. content: application/json: schema: allOf: - $ref: '#/components/schemas/McpSuccessResponseDto' - properties: data: $ref: '#/components/schemas/RegisterDeveloperResponseDto' '400': description: Validation error. content: application/json: schema: $ref: '#/components/schemas/McpErrorResponseDto' '401': description: Missing or invalid API key. content: application/json: schema: $ref: '#/components/schemas/McpErrorResponseDto' '409': description: Already registered as a developer. content: application/json: schema: $ref: '#/components/schemas/McpErrorResponseDto' '429': description: Rate limit exceeded. content: application/json: schema: $ref: '#/components/schemas/McpErrorResponseDto' security: - bearer-jwt: [] - api-key: [] components: schemas: RegisterDeveloperDto: type: object properties: name: type: string description: Name for the developer API key payoutAddress: type: string description: >- Legacy external payout wallet. Optional; agent fee claims credit the Echo Zero in-app wallet. developerProfile: description: Developer profile information allOf: - $ref: '#/components/schemas/DeveloperProfileDto' required: - name McpSuccessResponseDto: type: object properties: success: type: boolean example: true data: type: object description: Endpoint-specific payload additionalProperties: true required: - success - data RegisterDeveloperResponseDto: type: object properties: rawKey: type: string rawSecretKey: type: string developer: $ref: '#/components/schemas/DeveloperResponseDto' required: - rawKey - rawSecretKey - developer McpErrorResponseDto: type: object properties: success: type: boolean example: false error: $ref: '#/components/schemas/McpErrorBodyDto' required: - success - error DeveloperProfileDto: type: object properties: companyName: type: string description: Company or organization name website: type: string description: Company website URL contactEmail: type: string description: Contact email address DeveloperResponseDto: type: object properties: id: type: string name: type: string keyPrefix: type: string type: type: string rateLimitTier: type: string revenueShare: type: number payoutAddress: type: string description: Legacy field; agent fee claims use the Echo Zero wallet. betaStatus: type: string developerProfile: $ref: '#/components/schemas/DeveloperProfileDto' signalParsingAiPolicy: description: >- Environment-level parser AI policy used by the developer portal to disable per-agent overrides when a source is rules-only. allOf: - $ref: '#/components/schemas/DeveloperSignalParsingAiPolicyDto' developerAgentIds: type: array items: type: string scopes: type: array items: type: string status: type: string createdAt: type: string format: date-time stripeConnectAccountId: type: string description: Stripe Connect Express account id when onboarding started stripeConnectStatus: type: string enum: - pending - active - restricted description: Stripe Connect onboarding / payout readiness required: - id - name - keyPrefix - type - rateLimitTier - revenueShare - betaStatus - signalParsingAiPolicy - developerAgentIds - scopes - status - createdAt McpErrorBodyDto: type: object properties: code: type: string example: NOT_FOUND message: type: string example: Resource not found required: - code - message DeveloperSignalParsingAiPolicyDto: type: object properties: mode: type: string description: Global parser AI mode for sources where parser AI is enabled. enum: - 'off' - shadow - fallback telegramEnabled: type: boolean description: >- Whether Telegram signal-group messages may use parser AI under platform policy. discordEnabled: type: boolean description: >- Whether Discord signal-group messages may use parser AI under platform policy. webhookEnabled: type: boolean description: >- Whether inbound webhook text payloads may use parser AI under platform policy. Structured JSON payloads never use parser AI. required: - mode - telegramEnabled - discordEnabled - webhookEnabled securitySchemes: bearer-jwt: scheme: bearer bearerFormat: JWT type: http description: >- User JWT access token issued by `POST /api/auth/verify` or `POST /api/auth/social/verify`. Routes that accept both auth modes declare `api-key` *and* `bearer-jwt` security schemes. api-key: type: apiKey in: header name: x-api-key ````