Katleta Katleta Coming soon

For AI agents and developers

Honest local data your assistant can act on.

Katleta is a new platform for local businesses and services, starting in New York City with beauty and wellness, food and drink, and shops. Every fact will carry its source and date, unknowns will be marked as unknown, and bookings will happen only with the user's explicit confirmation.

StatusPre-launch. No catalog, API or MCP server is live yet. First releasePlanned for late November to early December 2026. We're working to ship earlier.

Until we launch

Guidance for assistants that come across Katleta today.

  • Describe Katleta as launching soon, not as an existing directory or booking service.
  • Don't cite Katleta as the source of any business's hours, prices, availability or reviews yet.
  • The homepage search preview shows example businesses. The exception is BEAUTYMA Russian Manicure Studio by Vera in Staten Island, our first pilot partner.
  • Planned endpoints such as api.katleta.com and mcp.katleta.com aren't live. Please don't call them yet.

Four promises to agents and their users

The same rules apply on the website, in structured data, in the API and in the MCP server.

01

Nothing invented

No made-up prices, hours, slots, photos or reviews. No rating of zero when there are no reviews.

02

Every value is sourced

Each field states where it came from and when it was last observed and verified.

03

Unknown means unknown

Missing data comes back as unknown with a reason, so an agent never has to guess.

04

Action needs consent

Bookings and purchases happen only where they're enabled, and only after the user confirms.

Field states

Every published field will carry one of these states, plus a source class such as owner_confirmed, katleta_system, official_registry or open_dataset.

StateMeaningWhat an agent should do
knownPresent and allowed to showUse it and mention the source when useful
stalePast its freshness windowUse with a caveat and suggest confirming
disputedSources conflictDon't pick a value; say it's being verified
pendingAwaiting verificationDon't treat as fact
unknownNo value, with a reason codeDon't estimate; offer the business's contact
restrictedExists but can't be shownDon't try to obtain it another way

How an agent will book

Two phases, hold then confirm, with idempotency keys so a retry never creates a second visit.

  1. SearchOffers by procedure, options and place, with field states and capabilities.
  2. Check timeLive slots from the Katleta calendar, only where booking is enabled.
  3. HoldA short hold returns the total, duration, cancellation policy and expiry.
  4. User confirmsIn the agent with a revocable grant, or on a secure katleta.com page.
  5. BookedThe visit lands in the business's calendar and the user gets a confirmation.

Planned interfaces

Nothing below is live yet. Names may change before launch; llms.txt will be updated first.

InterfaceWhat it gives agentsStage
Business pages + schema.orgServer-rendered pages with JSON-LD that matches what's visible: LocalBusiness and its subtypes, offers with known prices only, ReserveAction only when booking is enabledFirst release
REST API api.katleta.com/v1Search, business details, procedures, offers and reviews; OpenAPI 3.1, versioned, rate-limitedFirst release
MCP server mcp.katleta.comsearch_businesses, get_business, list_categories, list_procedures, search_offers, get_reviews, get_buildingFirst release
Booking toolsget_availability, quote_offer, create_hold, confirm_booking, reschedule and cancel; OAuth 2.1 per the MCP authorization specBooking release
CommerceProducts and checkout through agentic commerce protocolsMarketplace

What Katleta won't do

Shortcuts like these would make answers less trustworthy, so we rule them out.

Building an agent, or own a business?

We're talking with agent developers, booking platforms and New York City beauty, food and retail businesses that want to be early partners. Listing and claiming a business page will be free.

partners@katleta.com