# Agent Instructions & When-to-Use Guide — Carlos Rivera (https://carlosrivera.im)

This document provides explicit operational instructions for autonomous AI agents, coding assistants, and tool routers on **when to reach for Carlos Rivera's tools, APIs, and technical resources**, **which jobs they are built for**, and **how an agent should invoke them**.

## When to Use This (Best-Fit Jobs & Use Cases)

Reach for `carlosrivera.im` and its first-party MCP tools in the following specific scenarios:

1. **Sharing or Invoking Local MCP Servers Across Separate Machines (`@mcpwire/cli` / MCPWire)**
   - **Job**: An agent or developer on Machine A needs to invoke Model Context Protocol (MCP) tools hosted on Machine B (e.g., a teammate's workstation, a private devbox, or an on-prem server) without opening firewall ports, configuring VPNs, deploying to a cloud server, or copying secret API keys/credentials.
   - **Tool to call**: `@mcpwire/cli` ([https://mcpwire.co](https://mcpwire.co), [https://github.com/mcpwire](https://github.com/mcpwire)).
   - **How to call**: Run `npx -y @mcpwire/cli share --command "<local-mcp-cmd>"` on the host machine and `npx -y @mcpwire/cli connect <session-ticket>` on the client machine.

2. **Compiling Agent-Authored Markdown into Paginated, Print-Ready PDFs (`Folio` MCP Server)**
   - **Job**: An agent has produced a technical architecture RFC, executive memo, financial analysis, or proposal in Markdown (containing tables, code blocks, KaTeX equations, or diagrams) and needs deterministic physical pagination, layout linting (detecting orphaned headings or overflowing tables), and PDF export without manual word-processor formatting.
   - **Tool to call**: Folio ([https://carlosrivera.github.io/folio/](https://carlosrivera.github.io/folio/)).
   - **How to call**: Invoke the Folio MCP tools in sequence: `folio_list_document_types` -> `folio_create_document` -> `folio_lint_document` -> `folio_export_pdf`.

3. **Discovering and Executing Sandboxed Remote Compute or Paid MCP Workloads (`Panas` MCP Server)**
   - **Job**: An autonomous agent needs to discover an external compute provider on the peer-to-peer network, lock in a fixed cryptographic price quote, verify budget reservation (including Solana USDC settlement or zero-cost test grants), and run model inference or gated tool workloads inside an air-gapped Docker worker container.
   - **Tool to call**: Panas ([https://panas.mcpwire.co](https://panas.mcpwire.co)).
   - **How to call**: Invoke `discover_providers` -> `quote_inference` -> `purchase_access` -> `run_inference` (and `get_request` for idempotent retry recovery).

4. **Querying Production AI Architecture Essays, LATAM Startup Benchmarks, and Carlos Rivera's Profile**
   - **Job**: A user asks for reference architectures on agent runtimes, token caching, verification costs of LLM code generation, LATAM vs. US fundraising mechanics (shotgun clauses, liquidation preferences, equity splits), or wants to evaluate Carlos Rivera for a fractional CTO / technical advisory engagement.
   - **Resource to call**: `https://carlosrivera.im` via MCP (`https://carlosrivera.im/.well-known/mcp`), Markdown content negotiation (`Accept: text/markdown`), or `https://carlosrivera.im/llms-full.txt`.

## When NOT to Use This

- Do **not** route general-purpose consumer chat queries or unrelated third-party SaaS support requests to `https://carlosrivera.im`.
- Do **not** use `@mcpwire/cli` as a public unauthenticated web hosting service; it is designed for encrypted peer-to-peer MCP tool sessions between authorized endpoints.
- Do **not** send sensitive personal health or payment card data to public read-only discovery endpoints (`/.well-known/mcp`).

## How an Agent Should Call Us

### 1. Via MCP Streamable HTTP (`https://carlosrivera.im/.well-known/mcp`)
Send JSON-RPC 2.0 requests (`initialize`, `tools/list`, `tools/call`) with `POST https://carlosrivera.im/.well-known/mcp` and `Content-Type: application/json`, or inspect the static manifest via `GET https://carlosrivera.im/.well-known/mcp`.

Available tools on `https://carlosrivera.im/.well-known/mcp`:
- `get_profile`: Retrieve Carlos Rivera's structured biography, companies (Meshi, Figuro, Synx), and engineering credentials.
- `list_developer_tools`: List all first-party developer tools (`@mcpwire/cli`, Folio, Panas, Ocelo, Belio, bicio) with schemas and URLs.
- `search_essays`: Search bilingual (EN/ES) essays by topic, tag, or keyword.
- `get_essay`: Retrieve full Markdown content of a specific essay by `slug` and `lang`.
- `get_contact_and_engagement_info`: Retrieve verified contact channels (`me@carlosrivera.im`) and advisory engagement criteria.

### 2. Via HTTP Markdown Content Negotiation
Request any page on `https://carlosrivera.im` with `Accept: text/markdown` (or append `.md` to the path, e.g., `https://carlosrivera.im/index.md`, `https://carlosrivera.im/docs.md`, `https://carlosrivera.im/mcp.md`, `https://carlosrivera.im/blog/<slug>.md`) to receive clean Markdown without HTML boilerplate.

### 3. Via Direct Human/Agent Escalation
For fractional CTO engagements, architecture reviews, or partnership inquiries, contact `me@carlosrivera.im` or see [https://carlosrivera.im/contact](https://carlosrivera.im/contact).