Ganidhu Developer Portal

Quickstart

No API key is required for the current public endpoints.

curl -H "Accept: application/json" https://ganidhu.com/api/v1/profile
curl https://ganidhu.com/api/v1/resources

The complete OpenAPI 3.1 contract is available at /openapi.json. Each operation has a unique operation ID, typed response schema, and description suitable for function-calling adapters.

Markdown and agents

Agent-friendly text is published directly through /llms.txt, with expanded context in /llms-full.txt and dedicated guidance in /agent-instructions.txt. Use those files for text retrieval instead of scraping client-side state.

Authentication

The current API is unauthenticated and read-only. Do not send credentials or API keys. If authenticated or write-capable endpoints are introduced, the authentication method will be documented here and in OpenAPI before the endpoints are treated as public.

Rate limits and errors

Public API responses advertise a 120 requests per 60 seconds client budget using the current structured RateLimit and RateLimit-Policy fields, plus compatibility RateLimit-Limit, RateLimit-Remaining, and RateLimit-Reset fields. Clients should reduce request volume as the budget is approached and honor Retry-After on any future 429 response. API errors use JSON with a stable error code, human-readable message, and resolution hint. Unknown API routes return JSON instead of an HTML error page.

Webhooks, MCP, and sandbox

No public webhooks or MCP server are currently offered, and there is no separate write sandbox because every current endpoint is public and read-only. Use the production read-only endpoints for integration testing. Do not guess webhook or MCP URLs. When those interfaces exist, their canonical URLs and security requirements will be listed here, in llms.txt, and in the relevant schema.