# Obenan Scope: Company-domain orientation for https://www.obenan.ai Canonical root: https://www.obenan.ai Last reviewed: 2026-05-18 Freshness mode: manual-review Freshness note: The review date changes only when a human reviews and updates this orientation layer. It is not an automated content timestamp for the wider site. What Obenan is: Obenan is an agentic location management and business truth system for physical-location businesses. What Obenan does: It helps location-based brands stay current, structured, and actionable across public discovery surfaces, AI-facing environments, and merchant-domain machine-readable publishing. Operating interfaces: - Dashboard workflows for portfolio management, reporting, reviews, tasks, and governed location operations. - MCP for governed operations from compatible AI assistants and agent workflows. - Optional WhatsApp or chat-based updates and proof delivery where enabled. Platform coverage: - Human summary: 100+ directories and platforms - Exact counts: 104 total integrations, 100 currently updating, capability varies by destination and field - Full roster: https://www.obenan.ai/directories-and-platforms/ Apple Maps: - Obenan supports Apple Maps through the official Apple Business Connect API. - Core Apple Maps listing management is live now through Apple Business Connect API. Approval model: - Visible public routes are canonical truth. - If this orientation layer conflicts with a live public route, trust the live route. - Machine-readable companions support the visible route. They do not replace it. Freshness policy: - Freshness mode is manual review for v1. - The reviewed date changes only when a human updates this orientation layer. - Check the rendered public route before citing it. - Update this layer when the public capability map or route set changes. - Do not treat the reviewed date as an automated freshness signal for the wider site. Field authority: - Use Home, AI Visibility, and AI Presence for public company framing and the check, fix, prove story. - Use Merchant Infrastructure and Discovery for where Obenan sits relative to downstream commerce systems. - Use MCP for the governed conversational operating interface. - Use the solution pages for buyer fit by operating model. - Use About Us for company credibility and guide-role context. Citation guidance: - Cite the live visible URL when possible. - Prefer the visible public page over the machine companions when both are available. - Use the JSON twin for exact structured counts and capability summaries. - Do not infer indexing, training inclusion, or answer usage from these files. Machine artifact robots: noindex, follow Machine artifact rationale: Keep the machine files public and followable without letting them compete with the visible orientation page or become standalone public acquisition pages. Official artifacts: - /for-agents/: https://www.obenan.ai/for-agents/ (Human-readable capability map for the company domain.) - /for-agents.json: https://www.obenan.ai/for-agents.json (Machine-readable twin with structured capability and coverage data.) - /llms.txt: https://www.obenan.ai/llms.txt (Compact governance map and artifact index.) - /sitemap.xml: https://www.obenan.ai/sitemap.xml (Canonical XML sitemap covering all indexable public URLs across locales.) Technical references: - Nexus MCP documentation: https://nexus.obenan.com/mcp#overview (Technical documentation for connecting MCP-compatible assistants to Obenan.) Canonical public pages: - Home: https://www.obenan.ai/ (Company root and public category framing.) - AI Visibility: https://www.obenan.ai/ai-visibility/ (Why AI systems miss, misread, or under-trust a business.) - AI Presence: https://www.obenan.ai/ai-presence/ (Public audit flow for what AI can verify right now and what needs fixing.) - Merchant Infrastructure: https://www.obenan.ai/infrastructure/merchant-infrastructure/ (How Obenan sits upstream of booking, checkout, and payment systems.) - Discovery: https://www.obenan.ai/infrastructure/discovery/ (How agents query merchant truth with freshness and confidence boundaries.) - Agent Layer: https://www.obenan.ai/agent-layer/ (How approved AI assistants connect to Obenan to read, reason, and (with confirmation) act on location operations. Built on MCP.) - Directories and Platforms: https://www.obenan.ai/directories-and-platforms/ (Full public-safe roster of integrated destinations and exact coverage counts.) - Single Location: https://www.obenan.ai/solutions/single-location/ (Buyer fit for single-location operators.) - Multi Location: https://www.obenan.ai/solutions/multi-location/ (Buyer fit for portfolio and multi-location operators.) - Agencies: https://www.obenan.ai/solutions/agencies/ (Buyer fit for agencies and partner operators.) - About Us: https://www.obenan.ai/about-us/ (Company credibility, guide role, and public trust context.) - Pricing: https://www.obenan.ai/pricing/ (Commercial offer surface and plan comparison.) - Briefings: https://www.obenan.ai/briefings/ (Obenan Research index and signal briefings hub.) - Review Growth Calculator: https://www.obenan.ai/review-growth-calculator/ (Public review-growth calculator for merchant-fit signals.) - For Agents: https://www.obenan.ai/for-agents/ (Machine-readable orientation map for AI agents and assistants.) Briefings: - https://www.obenan.ai/briefings/merchant-owned-agents-acceptance-surface/ (Signal reading four May 2026 public moves (Mastercard Merchant Cloud Agent Suite, the Machine Payments Protocol specification wave at PaymentAuth, Circle Agent Stack, and the first live authenticated agentic transaction in Germany on Mastercard Agent Pay) as a shift toward merchant-owned agent surfaces and standardized agentic payment, while naming merchant-authored committability for local services as the upstream gap that remains unsolved. Obenan is not part of any of these products and does not process payments.) - https://www.obenan.ai/briefings/local-ai-visibility-moves-from-answers-to-actions/ (Flagship briefing reading two May 2026 public moves (Google AI Mode and Maps expansion into hotel booking and food delivery with a new Merchant Center AI performance insights surface, and an updated OpenAI ChatGPT Search help article documenting memory-aware query rewriting, exact location controls, mobile map output, and a restaurant action flow with prompt-prefill into a supported reservation provider) as one shift: local AI visibility is becoming a layered handoff problem with four operator lanes (crawl eligibility, recommendation presence, citation and source support, action-surface readiness), not a single citation number.) - https://www.obenan.ai/briefings/paid-agent-actions-are-becoming-infrastructure/ (Signal reading four May 2026 public infrastructure moves (AWS Bedrock AgentCore Payments, Stripe Sessions 2026 agent commerce stack, Machine Payments Protocol Internet-Drafts, Adyen joining the x402 Foundation) as a consolidation of payment-side infrastructure for paid agent actions, and naming merchant-side committability as the upstream gap that remains unsolved.) - https://www.obenan.ai/briefings/prepaid-local-services-practical-wedge-agentic-commerce/ (An Obenan Research briefing arguing that prepaid local services with bounded commitment objects (slots, tickets, tables, classes, bays, pickup orders, rental windows) are a practical wedge from agentic discovery into agentic payment because they require merchant-side truth before payment execution, with a two pilot lane recommendation and an explicit upstream-of-payment boundary; published 2026-05-01 by Obenan Research.) - https://www.obenan.ai/briefings/networks-are-building-the-bridge-merchants-still-own-the-truth/ (Flagship thesis on the April 2026 network-side bridges and the merchant-side truth that still lives inside the merchant.) - https://www.obenan.ai/briefings/mastercard-thailand-live-agentic-ride-booking/ (Signal reading the April 7 Thailand ride-booking transaction through merchant-participation criteria.) - https://www.obenan.ai/briefings/merchant-truth-before-agentic-payments/ (Foundational flagship thesis: merchant truth must be structured and current before agentic payment execution can be trusted.)