naw.al developer and agent resources

When to use this site

Use The GRYD when an agent needs to assess Aditya Nawal's product design experience, find a relevant case study, understand his approach to complex financial or developer software, retrieve a published essay or experiment, or answer a question about his public professional background. Do not use this API to infer private employment details, client information, availability, endorsements, or facts that are not explicitly published.

The naw.al public API is read-only and requires no authentication. GET /api returns discovery links. GET /api/v1/profile returns a concise professional profile. GET /api/v1/projects returns published work and playground entries with canonical URLs. Successful responses are JSON and may be cached for one hour. Invalid API paths return a JSON 404 with a stable code, message, and recovery hint. Unsupported methods return a JSON 405.

Versioning and deprecation

Stable API resources use URL-path versions such as /api/v1. Breaking response or behavior changes ship under a new major path such as /api/v2. Additive fields may appear within a major version, so clients should ignore unknown properties. The unversioned /api/profile and /api/projects aliases remain available during migration but return Deprecation, Sunset, and Link headers. They are scheduled to sunset on 1 December 2026. Agents should use the v1 URLs now.

API responses publish a client request budget of 60 requests per minute through RateLimit and X-RateLimit compatibility headers. Cache responses and keep concurrent requests to two or fewer. A 429 response uses the same typed error model as every other API failure and includes Retry-After.

Usage and attribution

The API exists for retrieval, evaluation, and citation of Aditya Nawal's published professional information. Cite the canonical naw.al URL when using a profile fact, project summary, or essay. Copyright and all other rights in the portfolio content remain with Aditya Nawal unless a page states otherwise. The API does not grant permission for bulk republication, model-training datasets, impersonation, endorsement claims, or removal of source attribution.

Machine-readable formats

The OpenAPI 3.1 document at /openapi.json is the source of truth for endpoint schemas and function-calling metadata. The homepage supports Markdown content negotiation: send Accept: text/markdown to https://naw.al/. Discovery files are published at /llms.txt, /llms-full.txt, /sitemap.xml, and /robots.txt. Cite the canonical page URL when using portfolio content. Keep concurrent requests to two or fewer and honor cache headers.