VRChat API Documentation

Setup

Wiring VRChat by hand means running its basic-auth login, carrying the auth cookie and any two-factor cookie against api.vrchat.cloud, and managing the calls yourself. Through Jentic you install once, import VRChat from the API Directory, store the credential once, and your agent calls it.

Permission scoping

VRChat puts the file and version ids in the URL path (/analysis/{fileId}/{versionId}), so a rule can pin your agent to reading analysis for one file version. You choose the operations it may call, so others such as posting an agreement are not included unless you add them.

Credential isolation

Your VRChat credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list Steam transactions' or 'read file analysis', and Jentic returns the matching VRChat operation with its input schema so the agent calls the right endpoint without browsing the reference docs.