WeCashUp is Not Agent-Ready to agents.
Discry independently scored how well an AI agent can discover and understand the WeCashUp API from what’s public — not whether it’s usable. Below: every signal we checked, what’s costing the score, and what to change.
SCORED UNDER RUBRIC 1.2 · A full re-launch under Discry Score 2.5 — a new behavioral instrument, not comparable to these scores — is in progress.
Discovery
45% of score · 26/100Comprehension
55% of score · 28/100What we found
- An agent starting from the brand domain would conclude the API is dead: www.wecashup.com is unreachable/parked (its sitemap lists a single '/lander' page), and the live docs at docs.wecashup.com are not linked from any discoverable surface.
- The documentation is a single JS-rendered Postman Documenter page — a naive fetch captures only ~2 of 10 sections (~53 endpoints); full content requires scripted scrolling and arrives polluted with Postman UI artifacts.
- Code examples would actively mislead an agent: a broken 'test/users/token' curl, base URLs mixing api.wecashup.com and api.wecashup.tech, and endpoints whose documented path differs from the path in their own example call.
- There is no machine-readable surface at all: no OpenAPI spec, no AGENTS.md, no MCP presence, and the file at /llms.txt is a robots-style AI-training policy rather than actual llms.txt documentation; GitHub SDKs are untouched since 2017.
- Positive: endpoint entries lead answer-first with method + URL + purpose, and nearly all ~53 endpoints carry request/response examples — but zero error docs, rate limits, or workflow guides means an agent discovers every boundary by failing.
What to change
Prioritized by impact on discoverability. You (or your docs platform) deploy these — Discry never touches your API.
- 01Publish a public OpenAPI spec for the ~53 documented endpoints — the single highest-impact discovery fix, and it would also resolve the path/base-URL contradictions in the examples.
- 02Revive or redirect www.wecashup.com to point at docs.wecashup.com, and replace the robots-style /llms.txt with a real llms.txt that titles the API and links its documentation sections.
- 03Move off the single-page Postman Documenter to static, crawlable per-section documentation (or at minimum publish an llms-full.txt export) so agents can fetch content without scripted browser scrolling.
- 04Fix the broken and inconsistent examples: the 'test/users/token' curl, api.wecashup.com vs api.wecashup.tech mixing, mismatched documented-vs-example paths, and field-name typos like 'total_amount_vat_ecluded' and 'receivert_email'.
- 05Document error responses with recovery guidance, rate limits, and at least one end-to-end payment workflow (auth → create payment → handle webhook/notification).
Execution coverage · INFORMATIONAL, UNSCORED
Whether an agent can actually complete a call and recover from errors is the deeper Audit layer — documented here, but not part of the Discry Score.
Only authentication is documented (Firebase-issued Bearer tokens with a refresh endpoint). No error format, rate limits, pagination, or idempotency documentation exists. A webhook_url field appears on payment requests, but webhook payloads and events are never documented — the docs even note anonymous payments receive no payment-status notifications.