Developers
Query structured, merchant-approved commerce data through a remote MCP server or commerce APIs. Provenance is attached to every field.
Connection and authentication
Integrate through MCP or the commerce APIs, authenticated with OAuth or an API key. Credentials and access settings are issued self-serve from the console.
MCP tools
- search_businesses — search merchant commerce data.
- get_business_profile — retrieve a complete merchant profile.
Profile schema
- Identity — name, description, location, service area and languages.
- Catalogue — products and services, with pricing and availability.
- Operations — hours, ordering, delivery, payment and lead times.
- Contact — official business contact channels.
- Credentials — registrations, licences and certifications, with their status.
- FAQ — questions and answers written or approved by the merchant.
- Exclusions — what the business does not offer.
Response format
Responses are JSON. Every fact carries a source URL, a status and a last-updated time. Missing data is returned empty, never inferred.
Information status
- Business-declared — stated by the merchant through a verified domain, the console or an uploaded file. Not independently checked.
- Official — confirmed by a named official source, such as a registry or licensing authority. Ti-bag does not currently verify against official sources, so regulated claims remain business-declared.
Open-source site tag
A drop-in tag that signals the Ti-bag crawler when added to a site. Onboarding completes when the domain owner verifies ownership through DNS.
Formal recognition
The MCP server and commerce APIs are being submitted for formal recognition across AI platforms. Any model or agent that supports MCP or standard APIs can integrate.
Equal access
All developers receive the same terms and rate limits. Payment does not affect ranking or placement.
End-user confirmation
Tools that send information to a merchant, such as a quote request, require confirmation from the end user.
Data use
Data is served to answer the end user’s query. Caching, storage and model-training permissions are documented in the console; other uses require permission.
Access logs
Access logs record which application queried which profile. Merchants see aggregate query volumes and the questions asked.
Rules for AI responses
- Structured data only — no instructions, recommendations or promotional text.
- Missing data is returned empty, never inferred.
- Every fact includes its source, status and last-updated time.
- The merchant is the source of every claim; Ti-bag structures, it does not author.
- Ranking uses relevance and status only. Payment has no effect on placement.
- Text intended to manipulate AI systems is removed or flagged; offending profiles can be suspended.
- All developers receive the same terms and the same rate limits.
- Business-declared data must never be presented as officially verified.