PocketSmith

Name: PocketSmith API
Brand: PocketSmith
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsSource ControlapiKey, oauth256 EndpointsREST

For Agents

Programmatically get the authorised user, get user. Covers 56 operations with apiKey, oauth2 authentication.

Use for: I need to the authorised user, I want to user, Search for user, Find all institution

Install Jentic One Beta

Connect the PocketSmith to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the PocketSmith, 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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.

Capabilities

What an agent can do with PocketSmith API.

Get the authorised user

Update user

Delete institution

Create institution in user

GET STARTED

Start building with PocketSmith API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use PocketSmith API for, with concrete tasks.

★ Developer Tools Operations

Use the PocketSmith to perform developer tools operations programmatically. The API provides 56 endpoints covering core functionality including get the authorised user, get user, update user.

Call GET /me to get the authorised user

Automated Accounts Management

Automate accounts operations by combining multiple PocketSmith endpoints. Agents can get user and then update user in a single workflow.

Call GET /users/{id} to get user, then verify the result

AI Agent Integration via Jentic

AI agents discover and call PocketSmith 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 apiKey, oauth2 tokens manually.

Search Jentic for 'get the authorised user', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

56 endpoints — pocketsmith provides programmatic access to developer tools functionality.

METHOD

PATH

DESCRIPTION

GET

/me

Get the authorised user

GET

/users/{id}

Get user

PUT

/users/{id}

Update user

GET

/institutions/{id}

Get institution

PUT

/institutions/{id}

Update institution

DELETE

/institutions/{id}

Delete institution

POST

/users/{id}/institutions

Create institution in user

GET

/users/{id}/institutions

List institutions in user

GET

/me

Get the authorised user

GET

/users/{id}

Get user

PUT

/users/{id}

Update user

GET

/institutions/{id}

Get institution

PUT

/institutions/{id}

Update institution

DELETE

/institutions/{id}

Delete institution

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

PocketSmith apiKey, oauth2 credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'get the authorised user') and Jentic returns the matching PocketSmith operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct PocketSmith integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Github

Alternative developer tools API

Choose Github when you need a different approach to developer tools operations

Alternative

Gitlab

Alternative developer tools API

Choose Gitlab when you need a different approach to developer tools operations

FAQs

Specific to using PocketSmith API through Jentic.

What authentication does the PocketSmith use?

The PocketSmith uses apiKey, oauth2 authentication. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.

Can I get the authorised user with the PocketSmith?

Yes. Use the GET /me endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the PocketSmith?

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 the authorised user through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'get the authorised user'. Jentic returns the matching PocketSmith operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the PocketSmith have?

The PocketSmith exposes 56 endpoints covering accounts, attachments, categories operations.