RYNE BENSONGet in touch

Hue Talent

An agent-first talent platform for modeling, talent and creative agencies. Every action works by chat or by button, and both run on the same backend.

Ryne Benson

Product · Talent management · 2 min read

Agency software makes people click through forms and menus to do simple things. Hue lets them say it instead: a manager can ask for a three-day booking or a list of open jobs that fit a talent, and the menus are still there for anyone who would rather click.

Agencies manage talent, clients, multi-day bookings and a shared calendar, and match talent against a daily feed of casting calls. Talent onboard in six steps, claim an @username, publish a profile and upload headshots, digitals and reels. A booker side for brands and casting directors is next.

How it works

One copilot, three personalities

A single agent serves every user type. The API puts the user, org and role at the top of each prompt, and the copilot adjusts what it offers to the person it's talking to.

Tools grouped by domain

Five FastMCP servers cover talent, bookings, calendar, clients and jobs, all behind an AgentCore gateway with Cognito machine-to-machine auth. The agent has no local tools at all.

A turn streams through DynamoDB

An API route starts a worker Lambda that calls the agent. Partial output lands in DynamoDB about every 150ms and a streaming Lambda pushes it to the browser.

Tool calls are visible

The executor emits markers as tools start and finish, rendered in chat as chips with their duration and token usage.

Decisions worth explaining

Chat and buttons share one code path

The screens call the same libraries the MCP tools call, so there is never a second implementation to keep in sync when a feature changes.

Tools fail closed

Every MCP tool re-checks membership in DynamoDB before it acts, so even if the model passes the wrong org, the call is refused.

Atomic multi-day bookings

A booking is a parent row plus one row per day, each copied under the agency, talent and client. The whole thing is written in one transaction and capped at 22 days to stay inside DynamoDB's transaction limit, while single days can still be edited or cancelled.

Resilient tool calls

A failed MCP call reconnects and retries once before surfacing an error, which keeps long conversations from dying on a dropped connection.

CI deploys only what changed

The pipeline diffs each push and re-registers only the MCP servers and agents that changed, or all of them when shared code moves.

By the numbers

  • 1 agent
  • 5 mcp servers
  • 28 mcp tools
  • 41 api handlers

The stack

  • Interface. Next.js, React, Tailwind CSS, shadcn/ui, Motion, SWR
  • Agents. Strands Agents, A2A, Bedrock AgentCore, Claude
  • Tools. FastMCP, AgentCore Gateway, Cognito M2M
  • Data. DynamoDB, S3, SSM
  • Platform. SST, Lambda, API Gateway, Cognito, ECS, X-Ray
  • Delivery. GitHub Actions, semantic-release