Add an affiliate from the API, then check the roster.

API and MCP access needs the Plus plan. Onboarding review in the admin is not one of the published MCP tools.

A merchant might ask an agent to add a new partner and confirm the person is on the roster. Creating the record is POST /api/v1/distributors in the OpenAPI file. The write body includes firstName, lastName, email, phone, address fields (street1, city, stateProvince, zip, country), sponsor, enroller, simpleCommPlanId, payPalId, and corpEntity with businessName when the affiliate is a business. The affiliate id is optional on create.

What the agent should not invent

• Tax ids are never returned on GET. The detail record has hasTaxIdOnFile. Set the id only with PUT /api/v1/distributors/{id}/tax-id.
• The published MCP tools do not include an approve-enrollment tool. Onboarding review is an admin feature.
• explain_workflow, search_help, and get_help_topic are help tools on the MCP server at https://directsales.software/mcp. They do not create the affiliate.

Confirm the person is there

After the POST succeeds, find_distributor resolves an affiliate by id, email, or name, and list_distributors pages the roster. GET /api/v1/distributors returns id, name, email, phone, whether they are active, and, on some companies, sponsor, enroller, and rank. POST /api/v1/distributors/{id}/terminate and reactivate change that active state.

The API guide says validation and side effects match the admin, including accrual, the registration email, and the audit log. Deactivating a real-time plan fails while affiliates are assigned to it.