For Agents
Programmatically get authenticated user profile, list accessible practices. Covers 17 operations with bearer authentication.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Socket API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fusesocket.com%2Fusesocket" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fusesocket.com%2Fusesocket" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with Socket API.
Get authenticated user profile
List accessible practices
Create a client
Query and filter Socket API records by parameters
GET STARTED
Use for: I need to authenticated user profile, I want to accessible practices, Search for specific practice, Find all a client
Not supported: Does not handle payments, communications, or crm - use for finance and accounting only.
Socket API provides read access to practices, proposals, and documents, and creation capabilities for clients and leads for accounting and bookkeeping professionals. The API exposes 17 endpoints secured with bearer authentication.
Monitor Socket API operational status and events
Patterns agents use Socket API for, with concrete tasks.
★ Finance and Accounting Operations
Use the Socket API to perform finance operations programmatically. The API provides 17 endpoints covering core functionality including get authenticated user profile, list accessible practices, get specific practice.
Call GET /api/user to get authenticated user profile
Automated Clients Management
Automate clients operations by combining multiple Socket API endpoints. Agents can list accessible practices and then get specific practice in a single workflow.
Call GET /api/v1/practices to list accessible practices, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Socket API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.
Search Jentic for 'get authenticated user profile', load the operation schema, and execute with Jentic-managed credentials
17 endpoints — socket api provides read access to practices, proposals, and documents, and creation capabilities for clients and leads for accounting and bookkeeping professionals.
METHOD
PATH
DESCRIPTION
/api/user
Get authenticated user profile
/api/v1/practices
List accessible practices
/api/v1/practices/{practice}
Get specific practice
/api/v1/clients
Create a client
/api/v1/clients
List clients
/api/v1/clients/{client}
Get client details
/api/v1/leads
Create a lead
/api/v1/leads
List leads
/api/user
Get authenticated user profile
/api/v1/practices
List accessible practices
/api/v1/practices/{practice}
Get specific practice
/api/v1/clients
Create a client
/api/v1/clients
List clients
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Socket API by hand means attaching its bearer token and moving between the user, practice, client, and lead endpoints yourself. Through Jentic you install once, import the Socket API from the API Directory, store the token once, and your agent calls it.
Permission scoping
Socket puts the practice and client ids in the URL path (/api/v1/practices/{practice}, /api/v1/clients/{client}), so a rule can pin your agent to one practice or client: it can read that record if you allow it. You choose the operations it may call, so creating clients or leads is not included unless you add it.
Credential isolation
Your Socket token 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 'get the authenticated user profile' or 'list clients', and Jentic returns the matching Socket operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Socket API through Jentic.
What authentication does the Socket API use?
The Socket API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I get authenticated user profile with the Socket API?
Yes. Use the GET /api/user endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Socket API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I get authenticated user profile through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get authenticated user profile'. Jentic returns the matching Socket API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Socket API have?
The Socket API exposes 17 endpoints covering clients, documents, leads operations.
/api/v1/clients/{client}
Get client details
/api/v1/leads
Create a lead
/api/v1/leads
List leads