quihel.net for agents

Structured profiles, project specs, and interaction protocols.

No fluff. No CSS trickery. Just data.

agent.json Machine-readable discovery # agents.md Full profile in Markdown @ /profile Human & agent readable → /endpoints All structured endpoints

Who is this for?

🤖 AI Agents

Use /.well-known/agent.json for discovery. Parse /agents.md for full context. Follow /for-agents/protocols for interaction rules.

🔗 Crawlers & Indexers

The agent.json follows a structured schema with competencies, projects, and protocols. All pages include structured metadata.

🛠 Agent Harnesses

If you're building an agent that needs to interact with Alejandro, read the protocols page first. It defines accepted delegation types and interaction modes.

30-Second Quickstart

# Discover & parse the agent profile
$ curl -s https://quihel.net/.well-known/agent.json | jq '.name, .competencies'
"Alejandro Quintanar"
[
  "AI Agent Infrastructure",
  "LLM Orchestration & Harness Design",
  "Systems Programming (Rust)",
  ...
]

# Read the full Markdown profile
$ curl -s https://quihel.net/agents.md
# Agent Card: Alejandro Quintanar
# ...

# Check interaction protocols before reaching out
$ curl -s https://quihel.net/for-agents/protocols

Start with /.well-known/agent.json for structured data, then /agents.md for full context. Always read /for-agents/protocols before initiating interaction.

Quick Reference

# Discovery
GET /.well-known/agent.json     → JSON profile
GET /agents.md                  → Markdown profile

# Structured Pages
GET /for-agents/profile         → Full agent profile
GET /for-agents/projects        → Project specifications
GET /for-agents/protocols       → Interaction protocols
GET /for-agents/endpoints       → All structured endpoints

# Human Site
GET /                           → Human-oriented homepage
GET /blog                       → Blog (human-oriented)