Sepal Concierge

Your agency keeps its agent. Residents get one front door.

Joining a regional front door doesn’t mean handing over your systems or your data. Your agent runs where you choose, reads only what you allow, and answers the orchestrator over the open A2A protocol. You decide what it shares, under a data-sharing agreement, and residents consent before any of their details reach you.

Four ways to join

PathBest forWhat it means
Build on Sepal ConciergeAgencies without an AI teamThe operator’s agency agent is the blueprint: point it at your pages, forms and address services, and Sepal hosts it. The City of Paloma Springs runs this way in the sample region.
Start from the Python ADK kitAgencies with developersA Google Agent Development Kit starter with the A2A server, an agent card, a read-only MCP tool, sandbox pre-fill, a Dockerfile, Kubernetes manifests and the conformance tests. Runs in your cloud.
Bring your own agentAgencies with an agent alreadyLangGraph, Semantic Kernel, Copilot Studio, Agentforce or a vendor’s platform — anything that speaks A2A and passes the conformance suite. The county in the sample region connects a LangGraph agent this way.
Start with a stubAgencies not ready yetA stub agent answers from your public pages with synthetic data so residents get a consistent experience now, and the real agent replaces it later without changing the front door.

The readiness assessment scores your agency on data, APIs, identity, security, hosting, staffing and governance, and recommends a path and an effort estimate.

The conformance suite

Every agent passes the same twelve checks before it receives traffic, and again every night — plus a thirteenth, that calls without credentials are refused, once the agent is past sandbox. Run them yourself from the staff console’s agent page, or from the Python kit’s tests in your own pipeline.

See it as a partner engineer

  1. The agent card is published, valid and served over HTTPS
  2. The card declares the Concierge profile extension (concierge/1)
  3. The card declares how callers authenticate
  4. Unknown methods return JSON-RPC error -32601
  5. Malformed messages return JSON-RPC error -32602
  6. message/send returns a task
  7. tasks/get returns the same task
  8. Unknown task ids return error -32001
  9. Results carry sections with citations from the agency’s own pages
  10. The agent answers in the language it was asked in
  11. The agent refuses to write to a live system (the write-back guard)
  12. The agent answers inside its declared time limit

What stays with your agency

  • Your systems

    Your agent reaches them through MCP tool servers you run. Live systems are read-only; pre-filled forms go to your practice system until you decide otherwise.

  • Your data

    The orchestrator sends only what the data-sharing matrix allows for your agency, and only after the resident consents. Everything else is withheld from the A2A message.

  • Your answers

    Your subject-matter experts review flagged answers about your services, and corrections go to your page owners.

  • Your choice of model and cloud

    Gemini, Claude or an open-weight model in your own data center — the front door doesn’t care, as long as the agent conforms.

Bringing a partner on?

We’ll run the readiness assessment with your partner’s IT team and stand up a stub agent the same week.

Talk to us