# Handyverse documentation > Choose the API for your integration, then read its agent instructions and OpenAPI spec. Each API has its own credentials, resource identifiers and supported operations. See [Using the docs with agents](https://links.handyfeeling.com/docs-guide-using-docs-with-agents) for read-only MCP connections, downloadable references and update checks. ## Signup and access For APIs requiring credentials, sign up and sign in at the [user portal](https://links.handyfeeling.com/user-portal), then issue an Application ID (`application_id`) or Authentication Key (`authentication_key`) for the API you need. If your account cannot issue credentials for an API, contact platform support about access to that API. Keep Authentication Keys on your server. An Application ID or client token for one API does not automatically authorize another API. Handy REST API v3 supports client-token issuance; Channel API v1 and Stream API v0 use their documented creation credentials and resource keys. An account access token and an API client token have different roles. Hosting API v2 upload and download operations require no signup or API credential. Calling Handy REST to play a hosted script still requires Handy REST credentials and device addressing. ## Combine APIs - Use Handy REST for device control, playback and device events. - Use Stream to store scripts or append live points, then pass its returned `stream_ref` to Handy REST's STREAM protocol for device playback. - Use Hosting to obtain a temporary script URL, then pass that URL to a playback setup that accepts URLs, such as Handy REST HSSP. - Use Channel to manage multicast memberships or pairing, then send supported Handy REST commands through the channel reference. Channel compatibility depends on the selected method and path. Read each selected API's instructions before constructing requests. Use its declared credential, transport, units and response envelope. For substantial integrations, consider generating a client in your preferred language from its OpenAPI spec; follow the guide for workflow requirements the generated client may not enforce. ## Agent instructions - [The Handy REST API v3 (stable)](https://links.handyfeeling.com/docs-handy-rest-api-v3-agents-md): Device control, synchronized playback, and device events. - [The Handy Channel API v1 (beta)](https://links.handyfeeling.com/docs-channel-api-v1-agents-md): Channel API for multicast groups, device subscriptions, and pairing. - [The Handy Stream API v0 (beta)](https://links.handyfeeling.com/docs-stream-api-v0-agents-md): Store scripts, append live movement data, and receive stream events. - [The Handy Hosting API v2 (stable)](https://links.handyfeeling.com/docs-hosting-api-v2-agents-md): Upload supported script files and fetch them through temporary URLs. ## OpenAPI specs - [The Handy REST API v3 (stable)](https://links.handyfeeling.com/spec-handy-rest-api-v3): Request and response schemas. - [The Handy Channel API v1 (beta)](https://links.handyfeeling.com/spec-channel-api-v1): Request and response schemas. - [The Handy Stream API v0 (beta)](https://links.handyfeeling.com/spec-stream-api-v0): Request and response schemas. - [The Handy Hosting API v2 (stable)](https://links.handyfeeling.com/spec-hosting-api-v2): Request and response schemas. ## Documentation updates - [The Handy REST API v3 (stable)](https://links.handyfeeling.com/docs-handy-rest-api-v3-version): Release identity and artifact checksums. - [The Handy Channel API v1 (beta)](https://links.handyfeeling.com/docs-channel-api-v1-version): Release identity and artifact checksums. - [The Handy Stream API v0 (beta)](https://links.handyfeeling.com/docs-stream-api-v0-version): Release identity and artifact checksums. - [The Handy Hosting API v2 (stable)](https://links.handyfeeling.com/docs-hosting-api-v2-version): Release identity and artifact checksums. ## Human guides - [The Handy REST API v3 (stable)](https://links.handyfeeling.com/docs-handy-rest-api-v3): Explanations and examples. - [The Handy Channel API v1 (beta)](https://links.handyfeeling.com/docs-channel-api-v1): Explanations and examples. - [The Handy Stream API v0 (beta)](https://links.handyfeeling.com/docs-stream-api-v0): Explanations and examples. - [The Handy Hosting API v2 (stable)](https://links.handyfeeling.com/docs-hosting-api-v2): Explanations and examples. ## Shared references - [Device and protocol compatibility](https://links.handyfeeling.com/docs-guide-device-protocol-compatibility-markdown): Documented device-family applicability, firmware requirements and the hardware ID/name reference. - [Using the docs with agents](https://links.handyfeeling.com/docs-guide-using-docs-with-agents-markdown): Connect to the read-only docs MCP or use downloadable agent instructions and OpenAPI specs. - [Estimating server time](https://links.handyfeeling.com/docs-guide-server-time-estimation-markdown): Implement client/server clock estimation with trimmed averaging or an offset-and-drift Kalman filter. - [Developer access](https://links.handyfeeling.com/docs-guide-developer-access-markdown): Create an account and obtain the credentials your API needs. - [Script formats](https://links.handyfeeling.com/docs-guide-script-formats-markdown): Read and write movement scripts as funscript JSON or Handy CSV. - [Demo videos and scripts](https://links.handyfeeling.com/docs-guide-demo-content-markdown): Ready-made synchronization videos and matching funscripts for HSP, HSSP and STREAM examples. - [Scripting](https://links.handyfeeling.com/docs-guide-scripting-markdown): Create and review scripts with the community tool or assisted scripting workflow. - [Scripting pipeline](https://links.handyfeeling.com/docs-guide-scripting-pipeline-markdown): Set up SFTP access and organize video uploads for assisted scripting. - [Script tokens](https://links.handyfeeling.com/docs-guide-script-tokens-markdown): Understand provider-controlled script access, distribution options, and playback handling. Documentation version: `2026.11.15.1`; tag: `docs-2026.11.15.1`. Use the selected API's update manifest to check its documentation revision and verify downloads.