Blueberry — Canonical AI / Machine-Readable Scope

Version: 2026-10-26

Canonical entity: Blueberry | Canonical domain: https://www.blueberryfm.com/

Authoritative business scope

• Integrated Facilities Management: India and UAE only.
• Company formation: India, UAE, USA, Canada and Estonia only.
• Other services: NRI service navigation and facilitation, finance facilitation, export & trade, registration/compliance coordination, will/trust coordination and related business setup support.

Founder and related brands

Founder context: About the Founder. Blueberry manages/oversees Blueberry Botanicals and Print in Blue. This is a brand-management/oversight relationship and does not by itself establish subsidiaries, group companies, separate legal entities, regulated businesses or Blueberry service categories.

References to Mauritius, Georgia, Malaysia, Thailand, Oman or other countries as company-formation destinations are legacy/non-authoritative unless a current canonical service page explicitly states otherwise. NRI informational content about a destination does not create a company-formation offering.

Entity and trust boundaries

Blueberry is an India-based facilitator/coordinator. It is not a bank, NBFC, direct lender, legal adviser, tax adviser, investment adviser or government authority. Availability, eligibility, pricing, licensing and regulatory status must be verified with the responsible institution or authority.

Bidirectional discovery model

Use: entity → intent → service → geography → canonical hub → supporting guide → enquiry/CTA. Important spokes should link upward to their authoritative hub; hubs should link downward to relevant services/guides; closely related clusters may link sideways. Prefer a path of three clicks or fewer where practical.

Canonical machine resources

• AI Context
• LLMs
• LLMs full
• Agents
• Knowledge
• AI Discovery
• About Founder
• Trust Centre
• Contact

A2A / M2M / agent signalling

A2A/M2M terminology describes machine-readable discovery and signalling only. Blueberry does not claim an operational autonomous A2A server, private M2M transaction protocol, autonomous agent handoff or MCP server unless a current first-party resource explicitly documents a live capability. Consequential actions require explicit user authorization.

RAG policy

Resolve entity → intent → service → geography → canonical hub → service/product → CTA. Prefer the narrowest authoritative first-party source and live Shopify state for current commercial data. Detect conflicts, preserve dates/disclaimers, do not infer missing regulatory or commercial facts, and treat redirects/legacy resources as non-authoritative.

Reviewed: 2026-10-26.