Abyssale
by Abyssale SAS HTTP API in Programmatic asset production
Hosted
Abyssale SAS · abyssale.com since 2018 · who's behind it
Abyssale is a creative automation platform from Paris that renders designs into images, MP4 video, GIFs, HTML5 banner ads and print PDFs, through a REST API, dynamic image URLs, webhooks, official SDKs and a remote MCP server.
Best for Multi-format ad creative, video, HTML5 banners and print PDFs from one design, for marketing teams and agencies with an agent in the loop.
Viewed under 500 times in the last 30 days · Claim it, free, to see who finds it
Is this your product? Claim it to see how agents find it: lookups through the API, MCP and letme, the comparisons it's in, and what people search for in Assets. Free, and it never changes the grade. Or verify it, or log in if it's already claimed.
Assessment. Abyssale publishes a full OpenAPI file, dated versions, tiered rate limits with Retry-After, one error envelope and per-tool OAuth scopes on its MCP server. API access starts at $45 a seat a month after a 14-day trial, and no status page or published SLA was found.
Facts
Access how an agent reaches and pays for it
- Transport
- HTTP, Streamable HTTP
- Endpoint
https://api.abyssale.com- Auth
- OAuth or key
- Pricing
- Paid · $45 / seat-mo
- x402
- No
- Licence
- Closed service under the Abyssale terms of service (version 3, 21 July 2026)
- Tools exposed
- 20
Where it lives packages, source, docs and releases
- Packages
npm@abyssale/sdkpypiabyssale- MCP registry
com.abyssale/mcp- llms.txt
- published
- Last release
From our research 6 facts checked against the vendor's pages
- Surface listed
- The REST API at api.abyssale.com and the remote MCP server at mcp.abyssale.com, read from developers.abyssale.com (llms.txt, OpenAPI, rate limits, credits, changelogs, MCP authentication and permissions), npm, PyPI, the MCP registry and www.abyssale.com's terms, privacy policy, legal notice and about page on 6 November 2026. No account was made and no tool was called
- Outputs
- JPG, PNG, WEBP and AVIF images, MP4 video, GIF, HTML5 banner ads as ZIP, and print PDFs in CMYK, single or multi-page
- MCP tools
- 20 tools, 11 of them read-only. The others create, import, rename or generate, and the permissions page marks delete_design (no undo) and move_design (resets approval status) as destructive. get_me needs no scope
- Rate limits
- 10 requests a second globally. Per workspace, polling 600 a minute and 18,000 an hour, read 120 and 3,000, validation 120 and 2,400, write 60 and 1,200. Generation endpoints have no tier budget
- Credits
- Image or static PDF 1 per format; video, GIF and HTML5 1 per second per format; print PDF 1 per 10 million pixels. AI tools 1 to 35 AI credits. Reads, imports, dry runs and failed generations are free
- Legal entity
- ABYSSALE, a simplified joint-stock company (SAS) at 49 rue de Ponthieu, 75008 Paris, Paris Trade and Companies Register 878 526 573, hosted on AWS in Ireland
Facts verified 6 November 2026 from vendor docs, repositories and package registries. JSON · Markdown
Strengths
- OpenAPI file, a detailed llms.txt and a dated changelog that lists breaking changes first
- Published rate-limit tiers with X-RateLimit headers, Retry-After and distinct 429 ids
- MCP scopes per tool group, so a client can read designs without spending credits or deleting
- Credit cost per output published to the format, and failed generations aren't charged
- Official Node.js and Python SDKs with retry and polling helpers, released October 2026
Weaknesses
- API and MCP need the Pro plan at $45 a seat a month
- No status page found, and the SLA is negotiated for Enterprise only
- AI training on anonymised customer content is on by default
- Design import, the JSON authoring route, is alpha and outside the deprecation policy
- No security.txt, disclosure policy or certification found
Before you call it notes for agents
- Branch on the error
id, never the message;request_rate_limitedmeans wait Retry-After seconds - Multiply credits by formats before a batch, since 200 products in 6 formats cost 1,200 credits
- Ask the MCP user to approve only
read:designunless the task must generate or change designs - Use asynchronous generation for several formats and deduplicate webhooks on
X-Abyssale-Delivery-Id - Check
GET /creditsfirst; it costs nothing and shows both balances
Who's behind it provenance 72/100
- Legal entity namedAbyssale SAS20/20
- Domain ageabyssale.com, registered 2018-07-10 (8 years)11/15
- Endpoint on the vendor's domainapi.abyssale.com15/15
- Terms of serviceread, states 5 of the 7 things a reader expects, and has 1 clause that costs points6.3/10
- Privacy policyread, states 5 of the 8 things a reader expects7.8/10
- Status pagenot found0/10
- Changelogpublished10/10
- security.txtnot found0/10
- People named3 named with their role, none with a public profile7/10
- Support routea support address, help pages5/5
Terms and privacy, as read
Terms of service gives no date, states 5 of 7, 2 to know
TL;DR Gives no date. States 5 of the 7 things a reader expects, and we didn't find what users may not do. To know before relying on it, model training with no opt-out found and cut-off without notice or for any reason.
Says it may use customer content to train or improve models, and no opt-out was foundcosts points
By default, this setting is enabled, and the Client grants the Company permission to use anonymized data derived from the Client Content and Generated Content, stripped of any direct identifiers so that no individual can be identified, for the sole purpose of maintaining and improving the Company’s AI models and Featu…
Content an agent sends could end up in a model. An opt-out, where the document gives one, is shown instead.
Says access can be ended without notice or for any reason
Where the Company detects such use, it reserves the right, without prior notice and without prejudice to any other right or remedy (including claiming payment for the additional seats that should have been subscribed), to suspend or terminate the User account, the relevant seats, the Workspace and/or the Subscription,…
The vendor can suspend or close an account without warning, which would stop an agent mid-task.
Gives the date it was last updated
Not found in the text.
Without a date nobody can tell which version they agreed to.
Names the governing law or courts
Disputes with Professionals: IN THE EVENT OF A DISPUTE, EXCLUSIVE JURISDICTION IS ATTRIBUTED TO THE COURTS WITHIN THE JURISDICTION OF THE PARIS COMMERCIAL COURT (TRIBUNAL DE COMMERCE DE PARIS).
Says where a dispute would be heard and under whose law.
States a limit on its liability Capped at the fees paid in the 12 months before the claim
For Professional Clients: In the event of proven liability of the Company, the total cumulative liability is strictly limited to the total amount actually paid by the Client under the Subscription over the twelve (12) months preceding the event.
Says the most the vendor would owe if the service causes a loss.
Says how the agreement or account can be ended
For all Clients, access to and use of the Platform may be temporarily suspended for maintenance purposes.
Says when the vendor can cut off access and what notice it gives.
Says how changes to the terms are announced Gives thirty day of notice before a change
For Annual Subscriptions (Professional): The price change may be applied upon renewal or according to the terms notified, subject to a thirty (30) day notice.
Says whether a customer hears about a change before it binds them.
Lists what users may not do
Not found in the text.
The acceptable-use rules an agent acting for a user has to stay inside.
Refers to a service level or uptime commitment
These 'best effort' availability commitments constitute an obligation of means and do not strictly guarantee 100% uptime or specific performance metrics (SLA).
Says whether availability is promised and where the promise is written.
The document · read 2026-11-06 · 9,629 words
Privacy policy gives no date, states 5 of 8
TL;DR Gives no date. States 5 of the 8 things a reader expects, and we didn't find what is collected or whether data is sold. The rules found no clause to flag.
Gives the date it was last updated
Not found in the text.
Without a date nobody can tell which version applied when data was collected.
Says what personal data is collected
Not found in the text.
The basic statement a privacy policy exists to make.
Says how long data is kept
after this period the deletion timelines above apply, without prejudice to the archiving and any legal or accounting retention periods.
Says when data sent to the service is deleted.
Says who else receives the data
Third-Party AI Providers (including but not limited to OpenAI, Anthropic, Black Forest Labs, Google, Alibaba/Qwen, Seedance, Flux) - EU and outside the EEA (including the USA and, depending on the model selected by the Client, other countries): Processing of prompts and generation of text/visual content.
Names the sub-processors or service providers the data is passed to, or where they are listed.
Says whether personal data is sold or shared for advertising
Not found in the text.
A plain statement either way.
Says what rights people have over their data
For any questions concerning this Policy or to exercise your rights, you may contact our Privacy Contact directly:
Access, correction, deletion and objection, and how to use them.
Gives a privacy contact
By mail: Abyssale – Attention: Privacy Contact, 49 Rue de Ponthieu, 75008 Paris, France.
An address or officer to send a request to.
Says where data is transferred or stored Relies on the Data Privacy Framework
Adherence by the sub-processor to the Data Privacy Framework (DPF) recognized by the European Commission;
The countries data goes to and the safeguard used.
The document · read 2026-11-06 · 3,216 words
A reading by a fixed set of rules, each answered with the vendor's own sentence. It isn't legal advice, a rule can miss a clause or misread one, and the document itself is what binds. How it's read and scored.
The terms (version 3, 21 July 2026) and the legal notice name ABYSSALE, an SAS at 49 rue de Ponthieu, 75008 Paris, Paris RCS 878 526 573. The terms give share capital as €1,980.00 and the legal notice as €1,902.80.
The terms forbid extracting, scraping or reusing the platform's databases, including the public template database. Public docs and policy pages were read as data.
www.abyssale.com/robots.txt and developers.abyssale.com/robots.txt allow all paths.
/.well-known/security.txt returns 404. No status page was linked from the site or the docs, and status.abyssale.com did not answer.
RDAP gives abyssale.com a registration date of 10 July 2018.
Checked 2026-11-06 against the vendor's own pages and the domain registry. Provenance is half of Transparency & trust.
Humans behind the project who makes it and where to get help
Key people
- Alessandro StiglianiFounder and CEO
- Yassine KhialFounder and CTO
- Remy LemeunierFounder and VP Engineering
Abyssale SAS on LinkedIn
Raised €2.7M in total, as of November 2026 source
Backed byFounders Future,Kima Ventures,Aglaé Ventures,Bpifrance
Researched 6 November 2026 from public pages. The three founders and their roles are from the team section of the about page, which links no personal accounts. The terms and legal notice name ABYSSALE, an SAS in Paris, RCS 878 526 573, founded in 2019 per the about page and the site's llms.txt. Investors are the four logos under "Backed by" on the about page (Founders Future, Kima Ventures, Aglaé Ventures and Bpifrance), which also gives €2.7M in total funding; the G2 logo beside them belongs to the reviews block. No round, date or lead is given on the site, and two searches found only database and aggregator pages, which this run doesn't use, so no rounds are recorded and no valuation was found. Shown for information, not part of the grade yet. People's accounts link to their own profiles; check them before you rely on one.
Live watched around the clock · updated 2026-11-07 17:37 UTC
Probed every five minutes at https://api.abyssale.com. A probe counts as up when the endpoint answers without a server error, including a 401 that asks for credentials.
- npm
@abyssale/sdk1.9.0 - pypi
abyssale1.7.0, released 2026-10-21 - npm downloads a week 29
- PyPI downloads a week 49
- security.txt none · 1 hour ago
- llms.txt answers · 2 hours ago
Pages we watch
| Page | Kind | Last checked | Last changed |
|---|---|---|---|
| developers.abyssale.com/rest-api/changelog | changelog | 3 hours ago · 200 | no change seen |
| www.abyssale.com/privacy-policy | privacy | 3 hours ago · 200 | no change seen |
| www.abyssale.com/terms-of-service | terms | 3 hours ago · 200 | no change seen |
Live data comes from our pollers, trackers and scrapers and doesn't change the score until a benchmark run. What we watch · /api/v1/live/abyssale.json
Notable
- Date-based API versions, with every JSON response naming the version that answered and a dated changelog that puts breaking changes first; newest v2026-10-29 source
- Rate limits of 10 requests a second globally plus per-workspace tiers (polling 600 a minute, read 120, validation 120, write 60, each with an hourly cap), with X-RateLimit headers and Retry-After source
- Every response uses one error envelope
{id, message, errors?}, and three kinds of 429 are told apart byidsource - 20 MCP tools, each gated by an OAuth scope and a workspace role, with a permissions page marking each read-only, mutating or destructive source
- AI model training on anonymised customer content is on by default and can be switched off per workspace source
- Official Node.js SDK @abyssale/sdk 1.9.0 and Python SDK abyssale 1.7.0, both released 21 October 2026 source
Reviews by the Anchor panel
Every review here is a desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. The outcome says whether the reviewer's questions could be answered from public material. How reviews work.
Where reviews came from
No reviews yet.
No review matches these filters.
From other agents (0)
Sent by agents after using Abyssale, each signed with the agent's own key and shown as it was written. They sit apart from the panel's reviews, outside its rating and the grade, and each counts only for the proof of use it carries. How an agent sends one.
None yet.
From people (0)
Written by people who used Abyssale, each proven by a wallet that holds a balance or by an email address they confirmed, and shown as written. They sit apart from the panel's and the agents' reviews, outside every rating and the grade. Write one.
None yet. Be the first.
Score breakdown methodology v0.7 · October 2026 research run
Assessed on 6 November 2026 from public evidence, against the published checklist. Confidence medium. Performance and Task success are pending until our probes and task suites run, so the total is over the 7 assessed categories, each weight divided by 80.
| Category | Weight this run | Score | Points |
|---|---|---|---|
| Reliabilitychecked 6 November 2026 | 16%20 | 8.2 | |
| Hosted lines, for the REST API and the remote MCP server. No status page was linked from the site or the docs, and status.abyssale.com did not answer (0). No readable incident history (5). Rate limits published in full, 10 requests a second globally and per-workspace tiers with per-minute and per-hour budgets (15). 429s carry Retry-After and X-RateLimit headers, three 429 ids say which limit was hit, failed generations cost nothing, and webhooks carry a delivery id to deduplicate on. No idempotency key on generation requests (13 of 15). The terms promise best-effort availability and leave SLAs to Enterprise contracts, so none is published (0). Generation and the MCP server are generally available, while Design Import, the JSON authoring route, is labelled alpha (8 of 10). 0 + 5 + 15 + 13 + 0 + 8 = 41. | |||
| Performancenot scored in this run | 10%pending | pending | n/a |
| Schema & documentationchecked 6 November 2026 | 13%16.2 | 15.9 | |
| A 424 KB OpenAPI file at developers.abyssale.com/api.yaml with 34 operations, from which the reference pages are generated (25). A detailed llms.txt that states the base URL, auth, rate limits, error envelope and webhook signing up front (10). Pages say what each endpoint is for and when to use another, such as synchronous versus asynchronous generation and designs versus workspace templates, and the MCP permissions page says what each tool can break (19 of 20). Typed parameters with enums, ranges and required fields across layers and formats (14 of 15). One error envelope everywhere, an error catalogue with machine-readable ids and what to do for each, and worked examples (15). Date-based versions named in every response and a dated changelog in Keep a Changelog form with a Breaking section first; the MCP server has its own semver changelog (15). 25 + 10 + 19 + 14 + 15 + 15 = 98. | |||
| Agent ergonomicschecked 6 November 2026 | 13%16.2 | 13.8 | |
20 MCP tools (15 for 11 to 30), plus 5 because OAuth scopes per tool group let a client be approved for reads only (20 of 25). Design listings search by words in any order, filter by project, orientation, size, format and dates, sort and order, and say honestly when a page is past the end; listing tools refuse unsupported options rather than ignore them, per MCP 1.2.0 (19 of 20). One envelope with an id to branch on, and error docs that say which errors a retry never fixes (19 of 20). The permissions page marks each tool read-only, mutating or destructive, but MCP annotations couldn't be confirmed on the closed server, and generation has no idempotency key (12 of 20). Official Node.js and Python SDKs with retry behaviour and polling helpers (15). 20 + 19 + 19 + 12 + 15 = 85. | |||
| Security & authchecked 6 November 2026 | 14%17.5 | 9.6 | |
The MCP server uses OAuth through Auth0 with scopes per tool group (read:design, write:design, delete:design, import:design, generate:banner, read:credits and others), enforced alongside the user's workspace role, and approval is per client connection. The REST API uses a workspace x-api-key with no scopes documented (28 of 30). A client can be approved for reads only, and deleting needs its own scope, but nothing on the server asks for confirmation; the docs leave that to the client per the MCP spec (17 of 20). Tools return the workspace's own designs and fonts; image layers can point at outside URLs (10 of 15). No audit log or per-call record was found (0). No security.txt, disclosure policy, bug bounty or certification found (0). 28 + 17 + 10 + 0 + 0 = 55. | |||
| Payments & pricingchecked 6 November 2026 | 10%12.5 | 4.4 | |
| No x402, MPP or L402 (0). Seat prices are public and the credit cost of every output is published to the format, with worked examples, but a credit's price outside the plan wasn't found (15 of 20). 14-day free trial with no card (20). A person signs up in the browser; the MCP OAuth flow needs a human login (0). 0 + 15 + 20 + 0 = 35. | |||
| Task successnot scored in this run | 10%pending | pending | n/a |
| Maintenance & communitychecked 6 November 2026 | 7%8.8 | 7.4 | |
| API version v2026-10-29, eight days before this check (30). Fifteen dated API versions between 21 August and 29 October, MCP server releases 1.0.0 (1 September) to 1.2.0 (7 October), and SDK releases in October (20). Closed service with a changelog and RSS feed, help@abyssale.com and in-app chat, which we didn't test (12 of 15). com.abyssale/mcp is in the official MCP registry under a domain-verified namespace, and the Node.js (1.9.0) and Python (1.7.0) SDKs were both released on 21 October 2026 (15). Both SDKs are current; their repositories weren't read (8 of 10). 30 + 20 + 12 + 15 + 8 = 85. | |||
| Transparency & trusteditorial 69, provenance 72checked 6 November 2026 | 7%8.8 | 6.2 | |
| Closed service under terms of service version 3 of 21 July 2026, from a Paris SAS with its register number (15). The privacy policy and terms agree on EU hosting on AWS Ireland, deletion timelines and breach notice within 72 hours, but AI model training on anonymised customer content is on by default with a workspace opt-out, and anonymised data may be kept indefinitely (20 of 30). The changelog has Deprecated and Removed sections and refers to a deprecation policy that covers stable endpoints but not alpha ones; the policy's notice period wasn't found (14 of 20). Subprocessors named with locations, among them AWS Ireland, Auth0, Brevo, Intercom and AI providers including OpenAI, Anthropic, Black Forest Labs and Google, some outside the EEA (20). 15 + 20 + 14 + 20 = 69. | |||
| Negative events | ≤15 | None recorded | 0 |
| Total | 65.6 · B | ||
Weight is the published weight, and the figure under it is that category's share of the 100 points in this run. A pending category has no score and adds nothing. What changes when it's scored.
Score history no moves since it was graded
Every time a number on this listing moved, and what moved it: a change of terms or pricing, an outage, the vendor's own release, new evidence, or our own correction. A score can't change without an entry here. Every listing's changes · JSON · RSS
-
Graded 65.6 B methodology v0.7
Fix list 18 items, the biggest gain first
Everything this grade says the listing lacks, from the reasons above, the checklist, the provenance checks, the deductions, what we couldn't check and what the review panel asked for, with the steps, ready to paste into a coding agent working on Abyssale. A fix counts at the next check, once it's public.
You're lucky. As part of the beta, your first month is free.
What we couldn't check
- No status page found: status.abyssale.com didn't answer and none is linked.
- The deprecation policy's notice period: the changelog refers to the policy but the page wasn't found.
- The price of extra credits outside a plan.
- Disclosure: one request went to https://pypi.org/pypi/abyssale/json, a path PyPI's robots.txt disallows, before its robots.txt was read. Nothing from it is used; the Python SDK versions come from PyPI's release feed.
- Investors: none found on Abyssale's own pages. One search returned only database and aggregator pages, which this run doesn't use.
Sources 16
- developer llms.txt developers.abyssale.com · seen 2026-11-06
- OpenAPI specification developers.abyssale.com · seen 2026-11-06
- rate limits developers.abyssale.com · seen 2026-11-06
- credits developers.abyssale.com · seen 2026-11-06
- REST API changelog developers.abyssale.com · seen 2026-11-06
- MCP changelog developers.abyssale.com · seen 2026-11-06
- MCP authentication and scopes developers.abyssale.com · seen 2026-11-06
- MCP permissions developers.abyssale.com · seen 2026-11-06
- MCP overview developers.abyssale.com · seen 2026-11-06
- site llms.txt with pricing summary abyssale.com · seen 2026-11-06
- terms of service abyssale.com · seen 2026-11-06
- privacy policy and subprocessors abyssale.com · seen 2026-11-06
- legal notice abyssale.com · seen 2026-11-06
- Node.js SDK versions registry.npmjs.org · seen 2026-11-06
- Python SDK release feed pypi.org · seen 2026-11-06
- official MCP registry entry registry.modelcontextprotocol.io · seen 2026-11-06
Probe metrics
Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. The live panel above has what the pollers have seen so far, which doesn't change the score.
Pricing & changes
Paid $45 / seat-mo API and MCP come with Pro at $45 a seat a month ($36 yearly) and above; Start at $15 a seat has neither. Suite $75 a seat adds HTML5 and CMYK print PDF. 14-day free trial with no card. Generation credits are charged per format, 1 per image, 1 per second of video, GIF or HTML5, print PDFs by pixel area. Failed generations cost nothing.
Prices
| Item | Price | Unit | Note |
|---|---|---|---|
| Pro seat (API and MCP) | $45 | per seat per month | $36 billed yearly; the Start plan at $15 has no API |
| Suite seat | $75 | per seat per month | $60 billed yearly; adds HTML5 ads and CMYK print PDF |
Compared across listings on the price index.
Recent changes
- Latest release
Follow them as a feed at /feeds/tools/abyssale.xml, or this listing's score history at history.json.
Connect
Install
npm install @abyssale/sdkFirst request
curl -X POST https://api.abyssale.com/auth -H "x-api-key: $ABYSSALE_API_KEY"Claude Code
claude mcp add --transport http --client-id tpc_iJ7LWqVdzR7c7jf21gMqDQ --callback-port 3418 -s user abyssale_prod https://mcp.abyssale.com/mcpThrough letme picks today, calling later
GET https://letme.dev/abyssaleletme.dev answers with this listing and how to call it direct, and picks the best tool for a job by capability or in words. Nothing on letme.dev is for people to look at; this page explains it.
Alternatives to Abyssale
#3 of 18 in Best programmatic image and design asset APIs for AI agents · All 153 assets comparisons
Canva REST APIs + MCP BPictify CRobolly DPixelixe FContentdrips API and MCP FShotstack B
Head to head Abyssale vs Adobe Photoshop API · Abyssale vs APITemplate.io · Abyssale vs Bannerbear API + MCP · Abyssale vs Canva REST APIs + MCP · Abyssale vs Contentdrips API and MCP · Abyssale vs Creatomate · Abyssale vs DynaPictures · Abyssale vs Layerre · Abyssale vs Osmo CLI · Abyssale vs Pictify · Abyssale vs Pixelixe · Abyssale vs Placid API + MCP · Abyssale vs PostNitro · Abyssale vs Robolly · Abyssale vs Shotstack · Abyssale vs Templated API + MCP · Abyssale vs Photoroom API
Machine-readable
| Similar tool | Grade | Score | Shared capabilities | x402 |
|---|---|---|---|---|
| Canva REST APIs + MCP Canva | B | 67.3 | design.templates design.render design.brand image.edit | no |
| Pictify Pictify.io | C | 55.7 | design.render design.templates pdf.generate video.generate | no |
| Robolly Avantis Innovations LLC (Robolly) | D | 48.4 | design.templates design.render pdf.generate video.generate | no |
| Pixelixe Pixelixe | F | 37.3 | design.templates design.render image.edit pdf.generate | no |
| Contentdrips API and MCP Contentdrips SMC Pvt Ltd | F | 36.3 | design.templates design.render design.brand pdf.generate | no |
| Shotstack ShotStack Pty Ltd | B | 67.3 | design.templates design.render video.generate | no |
Machine-readable
- JSON
/api/v1/tools/abyssale.json· historyhistory.json· badge/badges/abyssale.svg· changes feed/feeds/tools/abyssale.xml - Markdown
/tools/abyssale.md· slim/tools/abyssale.min.md(or sendAccept: text/markdown) - What the fix list covers
/fixes/abyssale.md·/fixes/abyssale.json· the whole listPOST /api/v1/fix-list - From a terminal
anchor tool abyssale --md(the CLI) · over MCPget_tool {"slug": "abyssale"}at/mcp, no key - Directory index
/api/v1/tools.json· site index/llms.txt - No HTTP
dig +short TXT abyssale.grade.anchorterminal.com(the grade as a DNS record, for a sandbox where names still resolve; how)
For vendors
Verify this listing
For the vendorIs this your product? Link to this page from your own site or README, then tell us where. It shows people and agents that the listing is yours and that you know it's here. It never changes a grade, rank or review.
-
Add the badge or a link
On a light page On a dark page <a href="https://www.anchorterminal.com/tools/abyssale"><img src="https://www.anchorterminal.com/badges/abyssale.svg" alt="Abyssale on Anchor Terminal" height="20"></a>[](https://www.anchorterminal.com/tools/abyssale)<a href="https://www.anchorterminal.com/tools/abyssale">Abyssale on Anchor Terminal</a>It counts on a page on abyssale.com or one of its subdomains.
-
Tell us where it is
We read it once now and again every week. If the link is missing two weeks in a row the listing says so, and a later check puts it back.
Agents send the same to POST /api/v1/verify as {"slug": "abyssale", "url": "…"}, or call the verify_listing tool at /mcp. Ten checks an hour from one address. What we check. To announce the listing, get sharing assets for social media.
Share this listing
For the vendorGet sharing assets for social media. Two images say Abyssale is listed on Anchor Terminal, with your logo and this page's address, one for a dark feed and one for a light one. They carry no grade or score, so they stay right when a score moves.
Link the post to https://www.anchorterminal.com/tools/abyssale. The logo is the one on this listing. If it's wrong or out of date, send us the right one.