CODAZEN_

Our own engineering — Harmonica

Connecting Meta models to an existing application

Integrating hosted Meta model access with chat, tools, session records, and application controls.

Context

Harmonica already had engineering workflows and access boundaries. Adding a hosted model provider needed to fit those workflows without replacing the application’s control over tools and credentials.

Approach

We implemented a dedicated Meta integration within the application’s provider and agent layers. Model selection and credentials remain explicit, while the surrounding workflow retains its own context and tool permissions.

Our role

The integration connects hosted Meta model access to chat, model-backed workflows, and tool-using sessions. It supplies the selected model and credentials and connects the tools available to the session.

Responses, tool activity, and usage are recorded within the workflow. Streaming behavior, authentication failures, and unsupported configurations are handled as application concerns, alongside the model request itself.

  • Hosted model API access
  • Tool calling and session records
  • Streaming and configuration failures

What this demonstrates

The implementation connects hosted Meta models to the context and tools of an existing product, with session records and provider-specific failure handling.

Explore the engineering

Meta AI integration

Bring experienced engineers into the systems and workflows where the challenge lives.

Explore Meta AI
← All work

Let’s put your next priority into production.

Tell us about the workflow, integration, or delivery challenge your team needs to move forward.

Discuss your next priority