buttplug.io valid
Buttplug
Spec and developer guide for Buttplug.io
For agents: Spec and developer docs for the Buttplug device-control protocol and Intiface ecosystem, including OutputCmd messages and device protocol reverse-engineering no
buttplug protocolintifacedevice controlprotocol specreverse engineering
- Authority
- 52 reach 7 · trust 5 · quality 25 · freshness 15
- Tier
- listed
- llms.txt
- https://buttplug.io/llms.txt
- llms-full.txt
- https://buttplug.io/llms-full.txt
- Sections
- 2
- Links
- 487
- Size
- 101686 bytes
- Popularity rank
- #351438
- Country
- Germany
- Categories
- APIs and SDKs · Documentation and reference · Open source projects
- For agents
- Documentation: developer or product docs worth reading, nothing to call
- Audience
- developers · agents can: read docs · en
- First seen
- 2026-10-19T10:42:43.878Z
- Last checked
- 2026-10-21T01:14:17.376Z
- Badge
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-21T01:14:14.299Z. Cached copy · Source on buttplug.io
# Buttplug
> Spec and developer guide for Buttplug.io
This file contains links to documentation sections following the llmstxt.org standard.
## Additional Resources
- [STPIHKAL - Device Protocol Documentation](https://buttplug.io/llms-stpihkal.txt): Protocol reverse-engineering docs for supported hardware devices
- [Dev Blog](https://buttplug.io/llms-blog.txt): Development blog posts and project updates
## Table of Contents
- [Architecture](https://buttplug.io/docs/spec/architecture.md): The goals of the Buttplug Protocol are fairly simple:
- [Spec Changelog](https://buttplug.io/docs/spec/changelog.md): - Nomenclature change: Standard -> API
- [Deprecated Messages](https://buttplug.io/docs/spec/deprecated.md): The following messages are considered deprecated, either because they've been duplicated by new
- [Device Discovery Messages](https://buttplug.io/docs/spec/device_discovery.md): Messages relating to finding and getting information about devices connected to the system.
- [Device Information Messages](https://buttplug.io/docs/spec/device_information.md): Messages that convey information about devices currently connected to the system. All of the following messages are sent Server -> Client, either i...
- [Connection Messages](https://buttplug.io/docs/spec/identification.md): Messages used for client/server connection lifecycle, including handshake and disconnection.
- [The Buttplug Intimate Device Control Protocol](https://buttplug.io/docs/spec/index.md): Buttplug Protocol Specification v4
- [InputCmd, InputReading, and InputType](https://buttplug.io/docs/spec/input.md): Getting data from devices is done via InputCmd. Within this message we encode all possible input information, making it simple to add new functiona...
- [Messages](https://buttplug.io/docs/spec/messages.md): Messages are the core object for Buttplug communication.
- [OutputCmd and OutputType](https://buttplug.io/docs/spec/output.md): Controlling devices is done via OutputCmd. Within this message we encode all possible output information, making it simple to add new functionality.
- [Status Messages](https://buttplug.io/docs/spec/status.md): Messages relaying different statuses, including communication statuses, connection (ping), log
- [Stop Messages](https://buttplug.io/docs/spec/stop.md): Possibly the most important messages in the system, stop messages stop connected devices from doing
- [Foreword](https://buttplug.io/docs/dev-guide/foreword.md): A few words from the author of this guide and architect of Buttplug.
- [Quick Start](https://buttplug.io/docs/dev-guide/getting-started.md): As a potential Buttplug Developer, the first thing you should do is...
- [Buttplug Developer Guide](https://buttplug.io/docs/dev-guide/index.md): Buttplug Developer Guide v4
- [Butts Are Difficult](https://buttplug.io/docs/dev-guide/intro/buttplug-ethics.md): > "… Society has put a lot of evils in our brains that we need to transcend before we make out."
- [Getting Help](https:
…Related sites
Other listed sites in APIs and SDKs. See the whole category →
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| ausca.com | Ausca | interface AI agents and MCP APIs and SDKs | 65 | ✓ | ✓ | ||
| agentwebmap.com | Agent Web Map | interface AI and machine learning AI agents and MCP +1 | FR | 60 | ✓ | ✓ | |
| wordpress.com | WordPress.com | interface APIs and SDKs | US | 75 | ✓ | ||
| hostinger.com | Hostinger | interface Design Infrastructure +2 | 73 | ✓ | ✓ | ||
| buffer.com | Buffer API | interface APIs and SDKs Productivity | 72 | ✓ | ✓ | ||
| openai.com | OpenAI Developers | interface Education Developer tools +3 | 72 | ✓ | ✓ | ||
| sentry.io | Sentry | interface DevOps and observability APIs and SDKs +1 | US | 72 | ✓ | ✓ | |
| stripe.com | Stripe | interface Finance and payments APIs and SDKs | IE | 72 | ✓ |
Machine-readable: GET /v1/resolve?q=buttplug.io · GET /v1/domain/buttplug.io · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage buttplug.io, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for buttplug.io:
1. POST https://agentwebmap.com/v1/sites/buttplug.io/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://buttplug.io/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/buttplug.io/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/buttplug.io).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.