A Brand Context Protocol (BCP) package gives your AI reusable guidance about a brand. It can inform copy, design, campaigns, and other work.
Current guidance from Encoded for using the Registry. This help page is separate from Aira’s published files and is not part of their signed publication.
Try it in your AI.
Copy the text below into a new conversation with web access. Add an actual brief if you have one, or let the AI ask what you want to make.
Help me use the Brand Context Protocol package at https://registry.encodedbrands.ai/brands/aira-be635173.
Open the entry page and briefly explain what this package can help me make and its publication status. If I have not supplied a brief, ask what I want to make, who it is for, and what it should achieve.
Use the relevant HTML sections linked from that page for my brief. Keep sourced guidance, inferred guidance, and gaps distinct. If the work needs brand assets, ask what approved files I can provide through connected sources such as Drive, Box, Adobe, an asset library, or an upload. Use only sources you can actually access with my permission.
Make the requested work, then briefly explain the important choices shaped by the sections you read. If a page cannot be read or is cut off, say which one and what is missing.
Bring the assets you have.
The package may not include every logo, font, photograph, or template available to your team. Share approved assets through your AI’s connected sources, a file upload, or an accessible link. Availability depends on the tool and your permissions.
Read the sections you need.
The package overview links to short HTML sections. If a long page is cut off, those individual sections offer a smaller read. The complete HTML package, JSON package, and original signed files remain available.
Public reading needs no Registry account. For ongoing use, the public MCP endpoint for this brand provides structured access in compatible tools. Saving or publishing changes is a separate authenticated workflow.
Keep the source in view.
The overview shows the record’s status and provenance. Brand-domain verification and file signatures have different meanings; neither turns inferred guidance into brand-approved policy. Older published onboarding and routing declarations remain available as source history. This page provides current Registry usage guidance without changing those files or granting an AI permission to act.
Legacy package: individually signed files; no publication-level manifest or committed revision ID is available.