> ## Documentation Index
> Fetch the complete documentation index at: https://developer.mogl.online/llms.txt
> Use this file to discover all available pages before exploring further.

# Agent workflow

> A role-based path for agents managing athletes, applying to deals, confirming availability, and handling payouts.

Agents use MOGL to manage athletes, support applications and availability, track deal execution, and maintain payout readiness for the roster. Agent workflows parallel athlete workflows while distinguishing actions performed on behalf of represented athletes.

## 1. Sign up

The updated signup work streamlined the agent flow and removed non-critical setup steps. API-based integrations should use the agent registration and authentication examples in the [Quickstart](/quickstart) and [Authentication](/authentication) pages.

## 2. Complete profile and roster setup

Agents need an account profile and roster context before they can manage athlete workflows effectively. Roster setup distinguishes between MOGL athletes and non-MOGL athletes where relevant, including which athletes can be acted on directly inside the platform.

Setup checkpoints:

* agent identity and contact fields complete;
* represented athlete roster connected or imported;
* athlete profile readiness visible;
* payout account status known;
* notification preferences configured.

## 3. Apply to deals on behalf of athletes

Agents can manage applications for represented athletes where permissions allow. The same application readiness checks apply: athlete profile completeness, social account requirements, eligibility, screening questions, and deal visibility rules.

The interface should clarify when an agent is acting as themselves and when they are acting on behalf of a specific athlete.

## 4. Confirm availability once hired

Agents can confirm availability for their athletes after hire, indicate that an athlete is unavailable, or request a new due date. If an agent has multiple athletes needing confirmation, confirmation prompts can appear one at a time from most recent to least recent.

Agent actions should be auditable because they affect the athlete, the brand, contract state, and deliverable timing.

## 5. Support deliverable execution

Agents need visibility into each athlete's hired deals, deliverable due dates, proof-of-work requirements, and status labels. The brand-facing labels should map cleanly to agent/athlete-facing states so support conversations do not depend on internal database values.

Useful deliverable states include In-Progress, Needs Approval, Resubmit Needed, Payment Processing, Paid, Voided, and Cancelled.

## 6. Manage payout readiness and reporting

Agent payout workflows use Stripe Express. Agents may need to complete onboarding, refresh expired account links, address requirements due, and review invoices or subscription details.

Reporting responsibilities often involve tracking campaign completion, athlete deliverable status, and payout state rather than campaign performance analytics alone.

## Related docs

* [Stripe payout setup](/features/payments/stripe-express-update)
* [Payments](/concepts/payments)
* [Availability confirmation and cancellation](/features/deals/athlete-availability-cancel-contract)
* [Core API Reference](/api-reference/core-api)