Build with agents

Use an AI agent to build event agendas, analyze event performance and create dashboards and reports with the Core API.

The Brella Core API skill helps an agent work with your event data: build an agenda, analyze a conference, prepare an exhibitor report or create a dashboard. It includes API references, task workflows and templates for both imports and read-only reporting.

A skill is a folder of instructions and references in the Agent Skills format, following the same approach as Supabase’s agent skills. It does not require Supabase or a Brella MCP server.

Install the skill

Download the skill bundle, extract it, and add the brella-core-api folder through your agent’s supported skill installation workflow.

The current bundle is version 1.2.0, including the event and organization insights workflow and interactive HTML report template. Replace an older installed bundle to use these capabilities.

For a coding project, agents that discover .agents/skills can load it at:

.agents/skills/brella-core-api/SKILL.md

Keep the bundled references and assets folders beside SKILL.md. Installing only the entrypoint loses the detailed API references.

With the skills CLI, you can install from the public archive:

npx skills add https://docs.brella.io/downloads/brella-core-api-skill.zip

Review the downloaded instructions before installation. Follow your team’s normal third-party tooling policy when running the CLI. The archive is hosted on this public documentation site; customers do not need access to Brella’s internal GitHub repository.

You can read the skill entrypoint and inspect the download checksum. Replace the installed bundle when you want the latest documentation; an existing download does not update itself.

What an agent can do

Your environment	What this enables
Chat or an agent that can read documents	Structure source material, identify gaps, draft a report from supplied exports and prepare API requests.
An agent with an authorized HTTPS tool	Fetch permitted event data or execute approved writes using your Core token.
An agent with data-analysis and file tools	Turn retrieved data or supplied exports into Markdown reports, CSVs, spreadsheets or interactive HTML dashboards.

ChatGPT and coding-agent skill support depends on the product and environment. See OpenAI’s skill documentation for supported installation locations, and GPT Actions for API connections. If your chat environment cannot load skills, attach the relevant Markdown guides. Live data retrieval still needs an authenticated API connection; a document-only chat can work from exports or prepare requests for a teammate to execute.

Start with a concrete task

I want to…	Start here
Turn notes into sessions, speakers and their connections	Create an agenda with an agent: a copyable prompt, planning template and interactive API recipe.
Recreate an event insights report for one event or an organization	Create an event insights report: detailed calculations, access gaps and an interactive HTML template.
Analyze a conference, review an exhibitor’s activity or plan the next event	Create dashboards and reports: five prompts, reporting scopes and a Markdown report template.

The agent uses the same Core API as a custom integration. It creates reports and dashboard files in its own environment; those files are not automatically hosted or shared.

Connect to your event

Ask your organization administrator for a Core API token restricted to the intended events, resources, actions and fields. Put it in your agent runtime’s secret store or local environment as BRELLA_API_ACCESS_TOKEN; set BRELLA_API_BASE_URL to the API origin supplied by Brella. Do not paste a token into a conversation or the public docs forms.

For reporting, use Read access to the required resources, fields and filters. Follow the reporting token example; Write permission is unnecessary. Keep credentials out of generated files.

For writes, approve the concrete plan and expected effects. Review one sample and reconcile the result before processing the rest. The skill helps an agent follow these steps; the API enforces the token’s actual permissions.

Documentation for machines

Documentation index.
Markdown pages: append .md to a documentation path, for example /cookbook/build-event-agenda.md.
Agent skill discovery index, using the discovery proposal adopted by Supabase. Client support varies; the archive download is the direct installation path.

The Markdown exports include the same request examples and field definitions as the interactive pages.