syndicate-issue-agent-key

Original：🇺🇸 English
Translated

Register an AI agent or autonomous publisher on the shipped Syndicate Links affiliate rail, store the returned affiliate key safely, and create tracking links with the live affiliate API.

3installs
Sourcecmcgrabby-hue/attribution-skills
Added on

NPX Install

npx skill4agent add cmcgrabby-hue/attribution-skills syndicate-issue-agent-key

Tags

Translated version includes tags in frontmatter
ai-agentaffiliate-marketingapi-integrationsyndicate-linkstracking-links

SKILL.md Content

View Translation Comparison →

Syndicate Links Agent or Affiliate Key

Use this skill when an AI agent, agent builder, or human publisher needs a Syndicate Links affiliate key and tracking links.
The shipped rail is 
affiliate
:
http
POST https://api.syndicatelinks.co/affiliate/register
POST https://api.syndicatelinks.co/affiliate/links
GET  https://api.syndicatelinks.co/affiliate/reports/conversions
Do not substitute draft-only publisher-named routes.

Prerequisites

  • An email address for the agent or publisher
  • A display name
  • Optional: website, agent platform, or agent ID
  • For tracking link creation: an approved partnership with the merchant program

1. Register as an agent affiliate

bash
curl -sS -X POST https://api.syndicatelinks.co/affiliate/register \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Example Shopping Agent",
    "email": "agent@example.com",
    "type": "agent",
    "agentPlatform": "custom",
    "agentId": "example-agent-v1",
    "website": "https://agent.example.com",
    "description": "Autonomous publisher that recommends merchant products when relevant."
  }' | python3 -m json.tool
Expected success is 
201 Created
with an affiliate profile and an 
apiKey
. Copy the key immediately. Treat it as a secret.
Accepted 
type
values are 
agent
, 
human
, and 
hybrid
. For AI agents, use 
agent
unless a human editorial surface is also involved.

2. Store the key securely

bash
export TOKEN="ak_live_sample"
Use your agent's secret store, environment manager, or deployment secret system. Never hardcode the key in prompts, repos, browser code, or public docs.

3. Create a tracking link

You need an approved partnership with the target merchant program before link creation succeeds.
bash
curl -sS -X POST https://api.syndicatelinks.co/affiliate/links \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "programId": "program_uuid",
    "destinationUrl": "https://merchant.example.com/products/widget",
    "sourceTag": "agent-recommendation"
  }' | python3 -m json.tool
The response includes 
trackingCode
. That is the code the merchant reports when it calls 
POST /merchant/conversions
.

4. List existing tracking links

bash
curl -sS "https://api.syndicatelinks.co/affiliate/links?programId=program_uuid&limit=10" \
  -H "Authorization: Bearer $TOKEN" | python3 -m json.tool

5. Check credited conversions

bash
curl -sS "https://api.syndicatelinks.co/affiliate/reports/conversions?limit=10" \
  -H "Authorization: Bearer $TOKEN" | python3 -m json.tool
Conversions can remain pending until the merchant payment window clears.

Common pitfalls

  1. Endpoint naming. Use the shipped 
    /affiliate/*
    routes for agent and publisher work.
  2. Key type. Affiliate keys are for link creation and reporting. Merchant keys are for firing merchant conversions.
  3. No approved partnership. 
    POST /affiliate/links
    returns 
    403
    if the affiliate is not approved for the program.
  4. Tracking code is not the key. The 
    trackingCode
    goes into the merchant conversion payload. The affiliate key stays in the Authorization header.
  5. Agent identity fields. For agents, set 
    type: "agent"
    and include 
    agentPlatform
    or 
    agentId
    when available.

Links