Abyssale MCP integration for AI agents.
Connect AI agents to Abyssale through 9 structured actions, including get banner, create dynamic image url, and generate banner. Review authentication, input…
- ACTION CONTRACTS
- 9
- 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 Abyssale integration exposes
The Abyssale Agent App exposes 9 provider-backed actions for design and marketing work. Its current contract lets an authorized agent retrieve metadata for an abyssale generated file, create or retrieve the dynamic image url for an abyssale design, and generate one abyssale image from a design using json element overrides and return the generated file metadata. 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 Abyssale account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Abyssale capabilities.
Showing 9 of 9 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_bannerREADRetrieve metadata for an Abyssale generated file.
INPUTS: bannerId
create_dynamic_image_urlWRITECreate or retrieve the dynamic image URL for an Abyssale design.
INPUTS: designId / enableRateLimit / enableProductionMode
generate_bannerREVIEWGenerate one Abyssale image from a design using JSON element overrides and return the generated file metadata.
INPUTS: designId / elements / templateFormatName / fileCompressionLevel
create_projectWRITECreate an Abyssale project to organize templates and generated images.
INPUTS: name
get_designREADRetrieve Abyssale design details including formats, elements, and variables.
INPUTS: designId
get_design_formatREADRetrieve detailed information for one Abyssale design format.
INPUTS: designId / formatSpecifier
list_designsREADList Abyssale designs available to the API key.
list_fontsREADList custom and Google fonts available in Abyssale.
list_projectsREADList Abyssale projects available to the API key.
INPUT CONTRACTS
Know what the action needs before it runs.
get_banner
bannerIdREQUIRED- The unique identifier of the generated file.
create_dynamic_image_url
designIdREQUIRED- The unique identifier of the design.
enableRateLimitOPTIONAL- Whether API rate limiting should be enabled for the image.
enableProductionModeOPTIONAL- Whether production mode should be enabled for the image.
generate_banner
designIdREQUIRED- The unique identifier of the design.
elementsREQUIRED- Abyssale element overrides keyed by layer name and forwarded to the generation endpoint.
templateFormatNameOPTIONAL- The format ID to generate when the design contains multiple formats.
fileCompressionLevelOPTIONAL- The percentage of compression to apply.
create_project
nameREQUIRED- The project name.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Banner
Retrieve metadata for an Abyssale generated file. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_bannerControl Create Dynamic Image Url
Create or retrieve the dynamic image URL for an Abyssale design. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_dynamic_image_urlVerify with Get Design
Retrieve Abyssale design details including formats, elements, and variables. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_designSAFETY BOUNDARY
Operate Abyssale with explicit limits
- Authorize Abyssale with API key and grant only the provider access required by the selected actions.
- 2 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- 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 Abyssale rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Abyssale task completed successfully.
CONNECTION MODEL
API key
Abyssale API key sent with the x-api-key header. Create or copy it from the API page in your Abyssale account: https://app.abyssale.com/api-key.
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
- 2
- 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 Abyssale.