# agents.txt — rules of engagement for AI agents
# XEKTA (Aumere, Inc.), San Francisco. Last updated: 2026-11-05.
# Longer, linked version: https://xekta.com/llms.txt

Name: XEKTA
Operator: Aumere, Inc.
What-we-are: The transaction layer between AI assistants and local businesses.
  First product: XEKTA Market, grocery and restaurant pickup. The buyer collects
  in person; XEKTA charges the saved card automatically at pickup — nothing
  to pay at the counter.
Status: XEKTA Market is live in San Francisco and Northern Virginia.
  Pickup only. Appointments, retail and delivery are coming, not live.

# Where to transact
MCP-Endpoint: https://mcp.xekta.com/mcp
Transport: Streamable HTTP
Auth: OAuth 2.1. Assistants that cannot do OAuth (e.g. Meta Muse): one-tap device link — POST https://mcp.xekta.com/assistant/device, the buyer taps Connect, poll POST https://mcp.xekta.com/assistant/token, then Authorization: Bearer <access_token>. Steps: https://mcp.xekta.com. No shared secret, no anonymous access.
Read-First: xekta://docs/start-here   # MCP resource, served after you connect
Human-Sign-In: https://mcp.xekta.com/account

# What this site is
# xekta.com is a public explainer with the connection steps. It carries no
# catalog, no prices and no stock: those come from the MCP endpoint.
Product-Feed: none
Public-API: https://mcp.xekta.com/mcp   # the MCP endpoint above is the only programmatic surface; no catalog listing needed

# Rules
Approval: The buyer approves each order themselves, in a confirmation box or on
  a signed-in link. An agent may not approve on the buyer's behalf, and a
  standing approval is refused.
Install: Nothing to install. No pip package, no global npm CLI. The npm package
  "xekta-mcp" is for operators hosting their own server, not for shoppers.
Invention: If a tool, URL, package or install step is not in the docs resource,
  it does not exist.
Freshness: Read price, stock, shop hours and service area with a tool call,
  never from cache or from an earlier answer.

Contact: info@xekta.com