Applications open now · General availability January 1, 2027

Your Business.

The AG Developer Program gives enterprise customers a configured developer environment and the AI coding tools to build dashboards, internal web apps, and mobile experiences directly against our APIs — on top of a backend, permissions matrix, and data model we already built for this industry.

Apply now See how it works

Enterprise accounts only during beta

  • The premise

    Every label, management company, and publisher runs its business a little differently. No single interface can serve all of them well.

  • The shift

    AI coding tools have made purpose-built interfaces inexpensive to produce. The constraint is no longer the UI — it is the backend beneath it.

  • Our position

    AG supplies the secured, scalable, industry-modeled backend. You supply the interface your team actually wants. That is the future of software.

01 — How it works

From account provisioning to production in three stages

  1. Provision the environment

    We configure a sandboxed developer organization mirroring your production tenant, with seeded data and scoped credentials.

    • Sandbox org + seeded roster data
    • OAuth client and scoped tokens
    • Developer MCP connected to your agent

  2. Build with your agent

    Your developer describes the interface in plain language. The agent writes against documented endpoints using our own product patterns as reference.

    • Web, mobile, or dashboard targets
    • Schema, contracts, and examples on tap
    • Permission errors surfaced at build time

  3. Ship to your team

    Promote from sandbox to production credentials. Authorization, audit logging, and scale are handled by the AG platform.

    • Production tokens on review
    • Audit trail on every mutation
    • Versioned API with deprecation policy

02 — What you can build

A platform that lets you design your UI/UX to your use cases

roster-exec-dashboard — production

Executive dashboard

Operational status of the entire roster, in one view

Leadership rarely wants the same screen the operators use. This build assembles release schedules, production timelines, touring activity, and open company projects into the review your C-suite actually runs — by artist, by quarter, by exception.

  • Milestones pulled live from projects, events, and tasks — no exports, no reconciliation
  • Exception view surfaces slipped dates and unstaffed dates before the weekly meeting
  • Read-only by design; leadership sees everything, changes nothing
  • roster:read
  • projects:read
  • events:read
  • financials:read

Built for

CEO, COO, and department heads

Replaces

A weekly deck assembled by hand from four systems

Screens in the build

  • Roster overviewgrid · 40 artists
  • Quarter timelinegantt
  • Exceptions queuelive
  • Artist detaildrill-down

tour-ops-mobile — staging

Internal application · mobile

Crew logistics for one tour, on the road

A touring party does not need the company system; it needs today. This build gives the crew day sheets, travel, advance detail, and settlement inputs on a phone, scoped strictly to the run they are on and syncing back into AG as the source of truth.

  • Day sheet generated from the routing already held in AG events
  • Crew updates write back to the same records the office is looking at
  • Access scoped to the tour — no path to the rest of the roster
  • events:write
  • tasks:write
  • contacts:read

Built for

Tour manager, production manager, and travelling crew

Replaces

Spreadsheets, group texts, and a shared drive of PDFs

Screens in the build

  • Today / day sheetmobile
  • Routing + travelmap
  • Advance checklistper show
  • Settlement captureoffline-safe

label-ops-workflows — production

Workflow tooling

The steps your team runs that no product ships by default

Every department carries nuances the native interface was never modelled around — an approval chain, an intake queue, a hand-off between two teams with different vocabularies. Build those as first-class screens for the people who live in them, on the same records everyone else uses.

  • Intake, approval, and hand-off states modelled to your process, not a generic one
  • One team gets a tailored interface without forking anyone else’s workflow
  • Every action lands in the same audit trail as the native application
  • tasks:write
  • projects:write
  • org:read

Built for

A single department — marketing, A&R ops, or business affairs

Replaces

Form threads, manual status chasing, and shadow trackers

Screens in the build

  • Intake queueassignment
  • Approval chain3 stages
  • Hand-off boardkanban
  • Team activity logaudit

03 — Security & permissions

Your application inherits the permissions matrix. It cannot exceed it.

Authorization is enforced at the API boundary, per organization, per role, per record — not in the interface you write. A developer building a tour app cannot read a royalty statement they were never entitled to, regardless of what the client code requests.

04 — Developer MCP

The model learns our API from our own product code

The AG Developer MCP server exposes our schema, endpoint contracts, and permission scopes to your coding agent — alongside real implementation patterns taken from the native Artist Growth application. Your agent writes against our APIs the way our engineers do, on the first attempt.

  • Full schema and endpoint contracts, always current with the platform
  • Implementation patterns lifted from the production Artist Growth codebase
  • Scope requirements stated per endpoint, so permission errors appear before runtime
  • Works with Claude Code, Codex, and any MCP-capable coding agent

ag-developer-mcp · tools

  • describe_schema entities, relations, field types
  • list_endpoints REST surface + required scopes
  • get_example native app implementation pattern
  • validate_request dry-run against permissions matrix
  • seed_sandbox representative roster fixtures
  • check_scopes what this token may actually do

05 — Enterprise

Custom API and MCP endpoints on request

If your use case reaches past our published surface, we will build to it. Enterprise participants can request dedicated endpoints, custom MCP tools, and schema extensions scoped to their organization, delivered and versioned by our platform team. We are open to feedback from everyone.

  • Dedicated API endpoints

    Purpose-built surfaces for workflows outside the published API, delivered and versioned by our platform team.

  • Custom MCP tools

    Org-specific tools added to the Developer MCP so your agent understands your extensions natively.

  • Schema extensions

    Additional entities and fields scoped to your organization, enforced by the same permissions model.

  • Solutions engineering

    A named engineer through your first production deployment, plus architecture review on request.

06 — Program timeline

Beta to general availability

  1. Now

    Applications open

    Enterprise accounts submit applications; review begins immediately in order received.

  2. Oct 2026

    First cohort provisioned

    Sandbox environments, scoped credentials, and Developer MCP access issued to selected participants.

  3. Nov – Dec 2026

    Beta build period

    Participants ship their first internal applications with solutions engineering support.

  4. Jan 1, 2027 (projected)

    General availability

    Program opens more broadly with published pricing tiers and self-serve environment provisioning.

07 — Apply

Request a place in the beta cohort

Applications are reviewed by our platform team in the order received. Participation during beta is limited to enterprise accounts in good standing; we will confirm environment eligibility and pair you with a solutions engineer before your sandbox is provisioned.

Response time —
five business days
Commitment —
one named technical contact or account executive
Cost during beta —
no additional license fee

08 — Questions

Frequently asked

Who is eligible during the beta?

Beta participation is limited to enterprise Artist Growth accounts. Applications from in-house engineering teams, technical leadership at partner organizations, and agencies building on behalf of an AG customer are all welcome, provided an enterprise account sponsors the work.

Do we need engineers on staff?

Not necessarily. Many participants pair a non-technical operations lead with a single developer, or with an agency partner. The environment, schema documentation, and Developer MCP are designed so that one competent developer using an AI coding tool can ship a working internal application.

What does the program cost?

Pricing tiers for general availability are still being finalized and will be published ahead of the January 1, 2027 launch. There is no additional license fee for participation during the beta period.

Which AI coding tools are supported?

Any tool that can consume an MCP server and write application code — including Claude Code and Codex. The Developer MCP is tool-agnostic; we validate against the major agents each release.

Can our application create and modify data, or only read it?

Both, within the scopes granted to it. Every action (CRUD) is subject to the same validation, audit trail, and permissions matrix as our native application.

What happens to what we build when AG ships new features?

Published API surfaces are versioned with a deprecation policy; your applications continue to run against the version they were written for. We strive to maintain backwards compatibility, and breaking changes are announced with a migration window and reflected in the Developer MCP.