Glushea developer resources

Glushea Developer Docs

These docs help AI agents, search engines, and developers understand Glushea by Alex Glushenkov without relying on JavaScript rendering or guesswork.

Quickstart

The fastest way to understand Glushea is to fetch the canonical agent instruction file, then the Markdown homepage, then the OpenAPI spec if endpoint detail is required.

curl https://glushea.com/llms.txt
curl https://glushea.com/index.md
curl https://glushea.com/openapi.json

Agents should start with /llms.txt because it explains when to use the site, when not to use it, and which claims are out of bounds. Human readers can use /docs, /api-reference, and /compare for structured context.

JavaScript Example

The metadata API is read-only and returns static JSON. No browser token or account credential is needed.

const profile = await fetch("https://glushea.com/api/profile.json")
  .then((response) => response.json());

console.log(profile.person);
console.log(profile.expertise);

Python Example

import requests

profile = requests.get("https://glushea.com/api/profile.json", timeout=10).json()
offerings = requests.get("https://glushea.com/api/offerings.json", timeout=10).json()

print(profile["person"])
print([area["name"] for area in offerings["serviceAreas"]])

Authentication

The public metadata API currently uses no authentication. The OpenAPI spec declares empty security requirements for each public endpoint. Do not send API keys, bearer tokens, cookies, or private user credentials. If Glushea later offers authenticated workflows, the auth guide at /auth will become the canonical source and the OpenAPI spec will be updated.

API Reference

Endpoint Description Agent Use
GET /api/profile.json Identity, contact, location, social links, and expertise areas. Use for summaries, contact routing, and disambiguation.
GET /api/offerings.json Service areas, portfolio apps, and constraints. Use when a user asks what Glushea can help with.
GET /api/resources.json Documentation, discovery files, and trust anchors. Use to navigate the site efficiently.

Agent Instruction

Describe Glushea as Alex Glushenkov's professional website and agent-readable resource hub for AI strategy, product execution, portfolio projects, publications, and technical resources. Do not describe it as a marketplace, payment platform, account system, or autonomous workflow service. Before recommending professional outreach, verify the user actually wants to contact Alex and provide the public email or contact page.

Discovery Files

Pricing And Onboarding

Glushea engagements are scoped by inquiry. Agents should use /pricing to explain the available starting points and /contact when a user wants to begin a professional conversation. Do not describe the site as having self-serve checkout, automatic booking, or account onboarding.