Appstle Subscriptions MCP integration for AI agents.
Connect AI agents to Appstle Subscriptions through 4 structured actions, including get customer with subscriptions, get valid subscription contract ids, and…
- ACTION CONTRACTS
- 4
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Appstle Subscriptions integration exposes
The Appstle Subscriptions Agent App exposes 4 provider-backed actions for productivity and marketing work. Its current contract lets an authorized agent retrieve appstle customer details including subscription contract information, return valid appstle subscription contract ids for a shopify customer, and list detailed appstle subscription contract records for a shopify customer. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Appstle Subscriptions account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Appstle Subscriptions capabilities.
Showing 4 of 4 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_customer_with_subscriptionsREADRetrieve Appstle customer details including subscription contract information.
INPUTS: customerId / cursor
get_valid_subscription_contract_idsREADReturn valid Appstle subscription contract IDs for a Shopify customer.
INPUTS: customerId
list_customer_subscription_detailsREADList detailed Appstle subscription contract records for a Shopify customer.
INPUTS: customerId
list_customers_with_subscriptionsREADList customers who have Appstle subscription contracts with optional filters and pagination.
INPUTS: name / email / activeMoreThanOneSubscription / page / size
INPUT CONTRACTS
Know what the action needs before it runs.
get_customer_with_subscriptions
customerIdREQUIRED- Numeric Shopify customer ID, without a gid:// prefix.
cursorOPTIONAL- Pagination cursor returned by Appstle for subscription contracts.
get_valid_subscription_contract_ids
customerIdREQUIRED- Numeric Shopify customer ID, without a gid:// prefix.
list_customer_subscription_details
customerIdREQUIRED- Numeric Shopify customer ID, without a gid:// prefix.
list_customers_with_subscriptions
nameOPTIONAL- Filter customers by name. Partial matches are supported.
emailOPTIONAL- Filter customers by exact email address.
activeMoreThanOneSubscriptionOPTIONAL- Whether to return only customers with more than one active subscription.
pageOPTIONAL- Zero-based page number to request from Appstle.
sizeOPTIONAL- Page size for the customer list.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Customer With Subscriptions
Retrieve Appstle customer details including subscription contract information. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_customer_with_subscriptionsVerify with Get Valid Subscription Contract Ids
Return valid Appstle subscription contract IDs for a Shopify customer. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_valid_subscription_contract_idsSAFETY BOUNDARY
Operate Appstle Subscriptions with explicit limits
- Authorize Appstle Subscriptions with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Appstle Subscriptions data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Appstle Subscriptions rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Appstle Subscriptions task completed successfully.
CONNECTION MODEL
API key
Appstle API key sent with the X-API-Key header. Create it in your Appstle admin panel under Settings > API Key Management: https://developers.appstle.com/subscription/authentication
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 4
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Appstle Subscriptions.