Cardly MCP integration for AI agents.

Connect AI agents to Cardly through 7 structured actions, including get balance, echo, and list credit history. Review authentication, inputs, workflows, and…

ACTION CONTRACTS
7
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 Cardly integration exposes

The Cardly Agent App exposes 7 provider-backed actions for marketing and productivity work. Its current contract lets an authorized agent retrieve the current cardly card credit and gift credit balances, send a json payload to cardly's authenticated echo endpoint for credential and request debugging, and list cardly account credit history records with pagination and time filters. 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 Cardly account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.

VERIFIED ACTION SAMPLE

Real Cardly capabilities.

Showing 7 of 7 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.

get_balanceREAD

Retrieve the current Cardly card credit and gift credit balances.

echoREVIEW

Send a JSON payload to Cardly's authenticated echo endpoint for credential and request debugging.

INPUTS: test / body

list_credit_historyREAD

List Cardly account credit history records with pagination and time filters.

INPUTS: limit / offset / effectiveTimeLt / effectiveTimeLte / effectiveTimeGt

list_fontsREAD

List Cardly fonts available for handwriting and text personalization.

INPUTS: limit / offset

list_gift_credit_historyREAD

List Cardly gift credit history records with pagination and time filters.

INPUTS: limit / offset / effectiveTimeLt / effectiveTimeLte / effectiveTimeGt

list_mediaREAD

List Cardly media options that can be used when selecting card products.

INPUTS: limit / offset

list_writing_stylesREAD

List Cardly writing styles available for generated handwriting.

INPUTS: limit / offset

INPUT CONTRACTS

Know what the action needs before it runs.

echo

testOPTIONAL
An optional query value that Cardly echoes back.
bodyOPTIONAL
An arbitrary JSON object to send to Cardly and echo back.

list_credit_history

limitOPTIONAL
The maximum number of records to return.
offsetOPTIONAL
The zero-based record offset to start listing from.
effectiveTimeLtOPTIONAL
Return records with an effective time before this YYYY-MM-DD HH:ii:ss value.
effectiveTimeLteOPTIONAL
Return records with an effective time before or equal to this YYYY-MM-DD HH:ii:ss value.
effectiveTimeGtOPTIONAL
Return records with an effective time after this YYYY-MM-DD HH:ii:ss value.

list_fonts

limitOPTIONAL
The maximum number of records to return.
offsetOPTIONAL
The zero-based record offset to start listing from.

list_gift_credit_history

limitOPTIONAL
The maximum number of records to return.
offsetOPTIONAL
The zero-based record offset to start listing from.
effectiveTimeLtOPTIONAL
Return records with an effective time before this YYYY-MM-DD HH:ii:ss value.
effectiveTimeLteOPTIONAL
Return records with an effective time before or equal to this YYYY-MM-DD HH:ii:ss value.
effectiveTimeGtOPTIONAL
Return records with an effective time after this YYYY-MM-DD HH:ii:ss value.

PROVIDER-SPECIFIC WORKFLOWS

Jobs this Agent App can support

Inspect Get Balance

Retrieve the current Cardly card credit and gift credit balances. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.

get_balance

Verify with List Credit History

List Cardly account credit history records with pagination and time filters. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.

list_credit_history

SAFETY BOUNDARY

Operate Cardly with explicit limits

  • Authorize Cardly with API key and grant only the provider access required by the selected actions.
  • The current action names appear read-oriented, but returned Cardly 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 Cardly rather than assuming unrestricted access.
  • After a call, inspect the structured result and execution record before reporting that the Cardly task completed successfully.

CONNECTION MODEL

API key

Cardly API key sent with the API-Key header. Cardly provides test and live API keys when API access is set up: https://api.card.ly/openapi/en-AU/2.2.0.

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
6
WRITE SIGNALS
0
HIGH IMPACT
0
REVIEW SIGNALS
1

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 Cardly.

Official Cardly website

ONE CONNECTION. REAL WORK.

Give your agent software it can use.

Connect through MCP or explore the Agent App catalog and choose only the capabilities your workflow needs.

EXPLORE AGENT APPS