Guides

How an offer becomes agent-ready on AgentSynta — and where it stops

An offer on AgentSynta becomes readable by AI agents only when a short list of your own switches are on. This guide walks through each one, shows what an agent actually receives, and is precise about what AgentSynta does not do.

Published by AgentSynta ·

The short version

AgentSynta publishes your business profile and offers as structured records at a public web address, through a REST API and through an MCP server at https://agentsynta.com/mcp. Each offer's record, looked up by its ID, is read fresh on every request. Search results, web pages and anything a crawler or assistant has already saved can lag behind your latest edit. An AI assistant can use those records once someone has connected it to AgentSynta, or when it reads the public web pages like any other site. AgentSynta does not push your offers into any assistant, and no assistant is connected to it automatically.

Step 1: publish your profile and turn on agent access

Two switches decide whether your business is visible at all:

  • Publish profile on the Profile page makes your public business page live.
  • Agent access on the Agent page lets agents read your business. With it off, agent search and offer records return nothing for your business.

Your public page needs both. If either is off, the page shows as not available and your offers are left out of the sitemap.

Step 2: choose what agents may do

On the Agent page you allow individual capabilities. Each is off until you turn it on:

CapabilityWhat it allows
Read business profileYour published name, description, location, contact details and any opening hours you added.
Search offeringsFind your published products and services, with prices where you set one. Required for agent search.
Check availabilityStock status and quantity, only for products where you track inventory.
Submit inquiriesAgents can send a question to your Inquiries inbox. They cannot order, pay, book or change prices.

Step 3: switch on a channel

On the Integrations page, turn on the REST API, MCP, or both. These control how software can reach your records. Switching one on makes your records available on that channel; it does not connect AgentSynta to any particular assistant. If REST is off, agents are not given REST links for your offers, and if MCP is off, the MCP tools leave your business out.

Step 4: publish the offer

Set an offer's status to Published. Drafts and archived offers are never shown. Each published offer gets a record keyed by a permanent ID that does not change when you rename the offer or change your business URL slug. The offer's web page address includes your business URL slug, though, so it changes if you change that slug. Agents and other software should keep the ID and look up the current record again to get the current page link. The dashboard's setup checklist shows which of these steps are still missing.

What an agent receives

When a connected agent searches, it gets the facts you published and nothing more. For example, a search for coffee under £20 returns records like:

name:        House Espresso Blend
type:        product
price:       12.50 GBP
business:    Example Roasters, Bristol
updated_at:  when you last changed it
record:      link to the current record, by permanent ID

(Illustrative example, not a real listing.) Stock appears only if you allowed availability and the product tracks inventory. AgentSynta does not add ratings, distance, delivery times or anything you did not enter. Agents are told to fetch the current record before quoting a price, because you may have changed it since the search.

Exact limits of platform connection

  • Connection is set up by the assistant's user or admin. Assistants that support custom MCP servers, such as ChatGPT, Claude, Gemini Enterprise or Copilot Studio, can be pointed at the AgentSynta MCP address. Whether that is possible depends on the person's plan and their organisation's admin settings.
  • Being listed is not being connected. AgentSynta is listed in the public MCP Registry. A listing makes the server findable by developers; it does not install it in anyone's assistant.
  • Search engines decide what they index. Your offer pages are server-rendered, listed in the sitemap and carry structured data, but no search engine or AI search product is obliged to crawl or show them.
  • Agents choose what to do with results. AgentSynta controls what it returns, not how an assistant ranks, summarises or presents it.
  • No transactions. AgentSynta never places orders, takes payments or books appointments.

Inquiries stay under your control

If you allow inquiries, a message lands in your Inquiries inbox for your team to read. Inquiries sent through the web form or the REST API must pass a short sum that helps reduce automated spam. AgentSynta does not reply on your behalf; you contact the person yourself and can mark the inquiry as replied. Read more in the real-estate use case.

Turning it off

Switch off Agent access or Publish profile and new searches and record lookups stop returning your business. Archive a single offer to withdraw just that one. Pages and lists that were already loaded, cached or saved elsewhere are not updated by this. Copies an assistant or search engine already saved are outside AgentSynta's control. Keeping things current is covered in keeping your offers accurate.

Create your business profile

Free to set up. Nothing is public until you choose to publish it.

Get started