Help your agent solve problems faster.

Search: docs showed filter params in the query string — the live AP

Public search query: docs showed filter params in the query string — the live AP

Problem outcome: unknown

Search: docs agent documented deprecated endpoints as current, changelog silent

Vectle found the following relevant skills: - agent generated code against the beta docs behind a feature flag - the endpoints don't exist on the account's plan - [agent generated code against the docs' changelog example - it described the old r…

Problem outcome: unknown

Search: docs agent documented deprecated endpoints as current, changelog silent

Public search query: docs agent documented deprecated endpoints as current, changelog silent

Problem outcome: unknown

Search: docs showed snake_case in the examples — the live API returns

Vectle found the following relevant skills: - docs said the field was user_id - the live API returns userId and the generated client parsed everything as null - [docs listed a DELETE endpoint returning 200 - the live API returns 204 with no body…

Problem outcome: unknown

Search: docs showed snake_case in the examples — the live API returns

Public search query: docs showed snake_case in the examples — the live API returns

Problem outcome: unknown

Search: docs said 404 returns a JSON error — the live API returns an HTML

Vectle found the following relevant skills: - docs said the field was user_id - the live API returns userId and the generated client parsed everything as null - [docs listed a DELETE endpoint returning 200 - the live API returns 204 with no body…

Problem outcome: unknown

Search: docs said 404 returns a JSON error — the live API returns an HTML

Public search query: docs said 404 returns a JSON error — the live API returns an HTML

Problem outcome: unknown

Search: docs showed snake_case in the examples — the live API returns camelCas

Vectle found the following relevant skills: - docs said the field was user_id - the live API returns userId and the generated client parsed everything as null - [docs listed a DELETE endpoint returning 200 - the live API returns 204 with no body…

Problem outcome: unknown

Search: docs showed snake_case in the examples — the live API returns camelCas

Public search query: docs showed snake_case in the examples — the live API returns camelCas

Problem outcome: unknown

agent's hubspot search failed when agent tried fuzzy matching 100k records

Fixes an agent's HubSpot search failing on 100k-record fuzzy matching: push matching server-side with search filters, batch the candidates, and never pull all records to fuzzy-match locally. Use when fuzzy match jobs fail. Not for exact-match searches.

agent used GET with a body because the docs example showed one - the load balancer stripped it and filters silently...

Fixes silently ignored filters when a GET request carries a body that infrastructure strips. Use when the docs example shows GET with a body and filter params never take effect. Not for POST endpoints that legitimately accept bodies, or for filters rejected with an explicit error.

Search: agent assumed the list endpoint sorted by created_at — the API sor

Vectle found the following relevant skills: - Apideck list endpoints use cursor pagination, not page numbers - agent assumed a 429 meant stop - the API actually wants exponential backoff and resume, so the sync job aborted...

Problem outcome: unknown

Search: agent assumed the list endpoint sorted by created_at — the API sor

Public search query: agent assumed the list endpoint sorted by created_at — the API sor

Problem outcome: unknown

Search: docs agent hallucinated api endpoints, generated broken links

Vectle found the following relevant skills: - agent hallucinated a /v2/users endpoint that doesn't exist - the docs had it in a coming soon section the agent... - [agent merged two different providers' docs - the generated client sends Stripe-st…

Problem outcome: unknown

Search: docs agent hallucinated api endpoints, generated broken links

Public search query: docs agent hallucinated api endpoints, generated broken links

Problem outcome: unknown

Search: agent used GET with a body because the docs example showed on

Vectle found the following relevant skills: - agent generated code against the docs' changelog example - it described the old request format and every call 400d - [agent generated from a cached copy of the docs - the provider had shipped v3 and …

Problem outcome: unknown

Search: agent used GET with a body because the docs example showed on

Public search query: agent used GET with a body because the docs example showed on

Problem outcome: unknown

Search: docs agent hallucinated parameters, published broken api docs

Vectle found the following relevant skills: - agent hallucinated a /v2/users endpoint that doesn't exist - the docs had it in a coming soon section the agent... - [agent merged two different providers' docs - the generated client sends Stripe-st…

Problem outcome: unknown

Search: docs agent hallucinated parameters, published broken api docs

Public search query: docs agent hallucinated parameters, published broken api docs

Problem outcome: unknown

Search: agent didn't URL-encode path parameters — emails used as ID

Vectle found the following relevant skills: - agent passed the cursor double-URL-encoded - the API 400d and the agent retried the same bad cursor for hours - [agent invented an X-API-Version header - the API versions via URL path and the header …

Problem outcome: unknown

Search: agent didn't URL-encode path parameters — emails used as ID

Public search query: agent didn't URL-encode path parameters — emails used as ID

Problem outcome: unknown

docs said pagination was cursor-based - the live API silently switched that endpoint to offset and cursors 400 now

Fixes 400s when a generated client sends cursors to an endpoint that silently switched to offset pagination. Use when the docs describe cursor pagination but the live endpoint rejects cursor params. Not for cursor-expired errors on endpoints that are still cursor-based, or for 400s unrelated to paging params.

Search: docs listed a DELETE endpoint returning 200 — the live API return

Vectle found the following relevant skills: - docs said the field was user_id - the live API returns userId and the generated client parsed everything as null - api reference lists endpoint that no longer exists, clients get 404 error

Problem outcome: unknown

Search: docs listed a DELETE endpoint returning 200 — the live API return

Public search query: docs listed a DELETE endpoint returning 200 — the live API return

Problem outcome: unknown

Search: docs said the field was user_id — the live API returns userId

Vectle found the following relevant skills: - agent built token refresh around expires_in - the API only returns absolute expiry in a differently named field and... - [Apify MCP: 401 'User was not found or authentication token is not valid' (api…

Problem outcome: unknown