Aspire
Connect Aspire to read influencer marketing results: creator posts, members, project performance, media value and creator payments.
You paste two values into PopMCP: an API key you create in Aspire's settings, and your Client ID, which is in your Aspire web address. A third value, an Atlas token, is optional.
- Setup time
- 2 min
- Auth
- API credentials
- API base URL
- https://public-api.aspireiq.com
- Rate limits
- Reports: Aspire does not publish a figure, and answers 429 with how long to wait. Atlas: 60 requests a minute per token.
Before you begin
- An Aspire account for the influencer marketing platform at aspire.io, with permission to manage integrations
- Optional: an Atlas token from your Aspire contact, if you want lookups of creators and posts through Aspire Atlas
Get your credentials
Create an API key in Aspire
Sign in to Aspire. Open Settings at the bottom left, then Integrations, then Aspire API, and click Create API Key. Give it a name like PopMCP. Under permissions, tick the read permissions: at least read:social, and read:member and read:payment for creator and payment data. Choose an expiry, or none. If you pick one, you will need a new key when it ends.
Create API Key
Name the key, pick its permissions and choose when it expires.
This view is a simplified sketch: the labels on your page may differ slightly.
Copy the key straight away
Aspire shows the key only once. Copy it before you click Done. If you lose it, you cannot get it back, so create a new one.
Copy your Aspire web address
While you are in Aspire, copy the address from your browser. Your Client ID is the part right after /client/. You can paste the whole address into PopMCP, and it picks out the ID for you.
Paste both into PopMCP
In PopMCP, paste the key into API key and the address into Client ID, then connect. PopMCP checks them with one small read of your posts. If Aspire gave you an Atlas token, it goes under More options. It starts asp_sa_. Leave it empty if you have none.
Decide which AI clients may use it
Every Aspire tool only reads, so no agent can change anything in Aspire or send a payment. Reports can include creator names and what they were paid, so tick Aspire on the PopMCP consent screen only for AI clients that should see them.
Connect in PopMCP
Open your workspace, choose Aspire in the marketplace, and fill in the connect dialog:
| Field | What to enter |
|---|---|
| API keysecret | From Settings, Integrations, Aspire API. Stored encrypted and only used on our server.Encrypted with AES-256-GCM on save and never shown again. |
| Client IDtext | Copy your browser's address while in Aspire and paste it here. We use the part right after /client/. |
| Atlas tokensecret | Optional. Adds lookups of any creator, post or tracked hashtag through Aspire Atlas. It starts asp_sa_ and comes from your Aspire contact. Lookups can spend Atlas credits.Encrypted with AES-256-GCM on save and never shown again. |
PopMCP verifies the credential against Aspire immediately. On success the connection flips to Verified and its MCP tools are provisioned.
Verify it worked
PopMCP marks the Aspire connection Verified and names it by your Client ID, because Aspire's API does not share workspace names. Ask the AI how your creators did last month to see real numbers.
Troubleshooting
"Aspire did not accept this API key..."
Why: The key was copied incompletely, has stray spaces, has expired or was revoked.
Fix: Create a new key under Settings, Integrations, Aspire API and paste it. A lost key cannot be shown again.
"Aspire accepted the key but it cannot read this workspace..."
Why: The key belongs to another workspace, or it lacks the read:social permission.
Fix: Check the Client ID comes from the same workspace as the key. Permissions are chosen when a key is made, so create a new key if one is missing.
Reports come back empty
Why: Aspire answers with an empty list for a Client ID with no data, a date range with no posts, or filters that match nothing. By default only posts published in the dates count.
Fix: Check the Client ID, widen the dates or drop filters. To count activity recorded in those dates, ask the AI to use the insight date.
An AI asks for a project ID
Why: Aspire's API has no list of projects.
Fix: Tell it the project's name: it can find the ID from tracked posts. The number is also in the project's Aspire address, after /project/.
"This tool needs an Atlas token"
Why: The Atlas tools use a separate credential, and this connection has none.
Fix: Ask your Aspire contact for a token and reconnect with it under More options. Your own workspace's reports do not need it.
An Atlas read says it is out of credits
Why: The Atlas billing account has used its credits. Nothing was charged for the refused call.
Fix: Ask your Aspire contact to add credits. Ask the AI to show your Atlas account to see the balance.
429 Too Many Requests
Why: Aspire limits how fast a key can call it. Atlas allows 60 requests a minute. Aspire does not publish a figure for reports.
Fix: Wait as long as the answer says, then try again.