Resources for assistants and agents
Structured information to identify abuenoben, understand when the service is a fit and inspect the public contact contract without mistaking it for an autonomous API.
When to use abuenoben
Use abuenoben when an agency, studio or B2B team needs senior technical delivery for a website, app, backend, API, CRM or integration with a clear scope, validation owner and handoff.
- An agency needs white-label or NDA-based technical capacity.
- A delivery already in motion needs senior ownership to reach closure.
- An Android/Kotlin app, backend or integration needs stabilization, QA or release support.
- A form, CRM, automation or data flow must become connected and traceable.
Automation boundaries
The documented API is the public contact form and requires a valid Turnstile verification issued by the website. It is not a bulk-submission channel and does not authorize fabricated tokens, anti-spam bypasses or secret transmission. An agent should bring the person to the form or prepare a brief for human review and submission.
Versioning and errors
Every response declares the dated contract version through API-Version. Errors use application/problem+json with the RFC 9457 model and retain stable codes for automation. An incompatible retirement will be announced in advance through Deprecation and Sunset headers.
Canonical resources
- llms.txt
Identity, fit, boundaries and priority links.
- llms-full.txt
Consolidated Markdown from public routes.
- openapi.json
OpenAPI 3.1 contract for the verified form.
- API catalog
RFC 9727 catalog for the endpoint and its documentation.
- auth.md
Authentication, human verification and form boundaries.
- sitemap.xml
Bilingual inventory of indexable URLs.
Is there a concrete delivery to assess?
Prepare the objective, current state, timing, validation owner and main blocker. The responsible person can review that brief and submit it through the protected form.