Technical Overview

GET  https://paki-api.elfresonero.workers.dev/status
POST https://paki-api.elfresonero.workers.dev/a2a
GET  https://paki-api.elfresonero.workers.dev/mcp
POST https://paki-api.elfresonero.workers.dev/mcp
GET  https://paki-api.elfresonero.workers.dev/.well-known/agent-card.json
GET  https://paki-api.elfresonero.workers.dev/.well-known/mcp.json
GET  https://cesaryague.es/works.jsonld
GET  https://cesaryague.es/works.txt

General catalogue browsing and public interaction do not require end-user authentication. Private and administrative routes are restricted and not documented here.

The agent card and the MCP manifest are also at https://cesaryague.es/.well-known/, which redirects to the addresses above. Agents should use the workers.dev addresses directly: many clients do not follow a redirect to another domain.

A2A

PaKi supports JSON-RPC 2.0 style agent-to-agent interaction for aligned agents. This includes catalogue dialogue, curatorial exchange, and interoperable discovery.

MCP

PaKi exposes the art catalogue through MCP using streamable HTTP transport.

Tools:
- search_artworks
- get_artwork
- recommend_for_space
- browse_collections
- catalog_overview
- rank_artworks
- request_inquiry
- confirm_inquiry

• Guide visitors through a catalogue of 297 seamless master loops across 15 collections plus Singles, enriched with 313 curatorial capsules.
• Answer technical questions about resolution, format, availability, and spatial suitability.
• Recommend artworks for hotels, galleries, spas, residences, clinics, and contemplative environments.
• Engage in multilingual dialogue, generally responding in the visitor’s language.
• Participate in A2A interaction with other agents.
• Provide MCP tool access to the structured catalogue.
• Accept real client enquiries via MCP and forward them directly to the artist, in two steps: request_inquiry shows exactly what would be sent, and confirm_inquiry sends it once the person named has agreed.

The main structured source for catalogue-level grounding is:

https://cesaryague.es/works.jsonld

The same catalogue as plain text, one line per work, light enough to read in one go: https://cesaryague.es/works.txt

PaKi also uses internally maintained curatorial context, curatorial capsules, and relational memory for conversation quality and workflow continuity.

• Public, without authentication: the endpoints listed above. Private and administrative routes require the artist’s key; without it, they answer as if they did not exist.
• Read and write: six of the eight MCP tools only read the catalogue. The other two handle enquiries: request_inquiry keeps a draft for two days, seen by nobody, and confirm_inquiry sends it — it stores the enquiry and notifies the artist — only after the person named has agreed to be contacted. No tool deletes or changes existing data.
• At the door: incoming messages pass a gate that turns away abuse before they reach a conversation.
• Data: no accounts and no tracking cookies. What is kept, for how long, and which services process it — Cloudflare, OpenAI, Telegram and IP-location services — is set out in the Privacy Policy.
• Infrastructure: PaKi runs as a Cloudflare Worker; the catalogue and these pages are static files on cesaryague.es.

To report a security concern, write to hello@cesaryague.es. No security certification is claimed on this page; organisations with regulated requirements should carry out their own review.

• Catalogue exploration and curatorial dialogue.
• Spatial and architectural recommendation, based on each work's measured physics.
• Agent-to-agent discovery and collaboration in aligned contexts.
• MCP access for assistants that want to query the catalogue as a tool.

PaKi is not intended to be a generic package manager library, an SDK, or a code-execution framework.

Public endpoint access is available for catalogue browsing and general interaction. Commercial pricing applies to the artworks: one-of-a-kind original acquisitions, directly from the artist's studio.