Dr. Amit Puri (amitpuri) Developer Resources & API Documentation

Official developer portal and machine-readable resources for amitpuri (Dr. Amit Puri). Discover programmatic REST APIs, OpenAPI 3.1.0 specifications, authentication guides, webhooks, Model Context Protocol (MCP) integrations, official CLI tools, RFC 9457 typed error models, rate limit response headers, and LLM context files.

OpenAPI 3.1.0 REST JSON API (/v1/ & root) RFC 9457 Problem Details RFC RateLimit Headers CLI Tool (@amitpuri/cli) MCP Server Support Webhooks & Auth llmstxt.org Standard CORS Enabled

1. OpenAPI 3.1.0 (Swagger) Specifications (amitpuri)

Agents and automated tools can inspect and consume our API definitions via OpenAPI 3.1.0 specifications at predictable, well-known URLs:

View openapi.json View openapi.yaml

# Fetch amitpuri OpenAPI JSON specification curl -s https://www.amitpuri.com/openapi.json | jq . # Fetch amitpuri OpenAPI YAML specification curl -s https://www.amitpuri.com/openapi.yaml

2. Public REST API Endpoints (v1 & Latest)

All endpoints support CORS, return UTF-8 JSON, provide structured schemas, and are available under both versioned paths (/api/v1/*) and root alias paths (/api/*).

Endpoint	Method	Description
`/api/profile.json` (or `/api/v1/profile.json`)	GET	Executive bio, titles, verified social links, and expertise domains for Dr. Amit Puri.
`/api/services.json` (or `/api/v1/services.json`)	GET	Advisory catalog, discovery call, and direct Topmate booking URLs.
`/api/projects.json` (or `/api/v1/projects.json`)	GET	Open AGI, Citizen Developer, Open Cloud, and designpattern.fyi initiatives.
`/api/health.json` (or `/api/v1/health.json`)	GET	API service health, timestamp, version, and documentation links.
`/api/deprecation.json` (or `/api/v1/deprecation.json`)	GET	API versioning lifecycle, Sunset/Deprecation header specifications, and 90-day grace period.

curl -s https://www.amitpuri.com/api/profile.json

3. Authentication & Authorization (amitpuri)

Public Endpoints: All public read endpoints (/api/*, /api/v1/*, /openapi.json, /llms.txt) are open and require no authentication or API key.

Enterprise & Webhook Access: For authenticated partner integrations, custom tool connectors, or webhook subscriptions, requests use standard Bearer Token authentication via the Authorization header:

Authorization: Bearer <YOUR_API_TOKEN>

To request enterprise API credentials, contact info@amitpuri.com.

4. Webhooks & Event Delivery (amitpuri)

Automated event delivery for advisory schedule updates, new publication releases, and architectural guideline alerts:

Payload Format: Standard JSON payload delivered over HTTPS POST.
Signature Verification: Webhook deliveries include an X-AmitPuri-Signature header (HMAC SHA-256) computed using your webhook secret.
Retry Policy: Failed deliveries are retried exponentially over 24 hours (1m, 5m, 15m, 1h, 6h, 24h).

# Example Webhook Payload Structure { "event": "publication.published", "timestamp": "2026-08-22T00:00:00Z", "data": { "title": "Citizen Developer Architecture Pattern", "url": "https://www.amitpuri.com/citizendeveloper" } }

5. Model Context Protocol (MCP) Server & Manifest (amitpuri)

Connect Dr. Amit Puri's advisory knowledge, publications, and tools directly to Claude Desktop, Cursor, Antigravity, or any Model Context Protocol client.

View .well-known/mcp.json View /mcp/manifest.json

Standard Discovery Manifest Endpoint

Clients can auto-discover server capabilities at https://www.amitpuri.com/.well-known/mcp.json (RFC standard discovery endpoint).

MCP Configuration (Claude / Cursor / IDE)

{ "mcpServers": { "amitpuri": { "command": "npx", "args": ["-y", "@amitpuri/cli", "mcp"] } } }

Streamable HTTP Transport (Remote Agents)

{ "mcpServers": { "amitpuri-remote": { "url": "https://www.amitpuri.com/api/v1", "transport": "http-streamable" } } }

Exposed MCP Tools & Resources

amitpuri://profile: Retrieve Dr. Amit Puri's verified executive bio, credentials, and contact endpoints.
amitpuri://services: Query available advisory sessions, workshops, and booking links.
amitpuri://projects: Query Open AGI, Citizen Developer, and cloud architecture initiatives.
amitpuri://llms-txt: Retrieve LLM routing rules and context triggers.
get_advisory_booking_url: Tool returning direct Topmate URLs for specified focus areas (AI strategy, low-code, cloud).
check_api_health: Tool returning API operational status and versioning metadata.

6. Official CLI Tool (npx @amitpuri/cli)

Developers and agents can execute the official CLI tool with zero installation:

# Run help npx @amitpuri/cli --help # Display profile & contact links npx @amitpuri/cli profile # List advisory services and booking links npx @amitpuri/cli services # List key initiatives and publications npx @amitpuri/cli projects # View agent calling guidelines & LLM context npx @amitpuri/cli agent

7. Typed Error Model (RFC 9457 application/problem+json)

All 4xx and 5xx error responses conform strictly to the RFC 9457 (and RFC 7807) Problem Details standard with typed error schemas for deterministic agent handling:

{ "type": "https://www.amitpuri.com/api/errors/not-found", "title": "Not Found", "status": 404, "detail": "The requested API endpoint does not exist on amitpuri.com.", "instance": "/api/404.json", "code": "API_ENDPOINT_NOT_FOUND", "recovery": { "openapi_spec": "https://www.amitpuri.com/openapi.json", "developer_resources": "https://www.amitpuri.com/developers" } }

8. Rate Limiting & Response Headers

To ensure high availability and fair use, public API endpoints implement standard RFC rate limit headers:

Header	Description	Example
`RateLimit-Policy`	Quota policy definition (limit and window in seconds).	`60;w=60`
`RateLimit-Limit`	Maximum allowed requests in the active window.	`60`
`RateLimit-Remaining`	Remaining request quota in the active window.	`59`
`RateLimit-Reset`	Seconds or timestamp until the current rate quota resets.	`0`
`Retry-After`	Returned on HTTP 429 responses indicating seconds to pause before retrying.	`60`

curl -i https://www.amitpuri.com/api/health.json

9. API Versioning & Deprecation Policy (amitpuri)

Our REST API follows strict semantic versioning and predictable lifecycle management. Read the complete API Deprecation Policy (/deprecation):

URL Path Versioning: The current active release is version v1. Endpoints are accessible at both /api/v1/* and aliased at /api/* for convenience.
Header Versioning: Responses return API-Version: v1. Clients may also supply an API-Version: v1 header.
Deprecation Signals: When an endpoint is deprecated, responses will include standard Deprecation (RFC 9745) and Sunset (RFC 8594) HTTP headers indicating the retirement timeline.
Grace Period: Deprecated APIs maintain a minimum 90-day transition window prior to sunset.
Policy Endpoints: Machine-readable policy available at /api/deprecation.json (and /api/v1/deprecation.json).

# Probing versioned endpoint curl -s https://www.amitpuri.com/api/v1/health.json

10. Agent & LLM Context Files (amitpuri)

Standardized machine-readable guidance for AI agents, crawlers, and tool-calling systems:

Resource	Format	Purpose
`/llms.txt`	Text / Markdown	LLM guidance per llmstxt.org standard with 'When to Use' triggers.
`/llms-full.txt`	Text / Markdown	Full knowledge base and extended context for autonomous agents.
`/agent-instructions.md`	Markdown	Explicit agent routing rules, tool-calling formats, and citation policies.
`/index.md`	Markdown	Markdown homepage for `Accept: text/markdown` content negotiation.
`/about`	HTML / Trust Anchor	Comprehensive background, career milestones, and leadership credentials.
`/contact`	HTML / Trust Anchor	Direct contact channels, Topmate booking hubs, and consultation routing.
`/privacy`	HTML / Trust Anchor	Privacy policy, transparency notes, and data handling standards.
`/sitemap.xml`	XML	Canonical sitemap for search engines and web crawlers.