Install Jentic One Beta

Connect the Splitwise API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Splitwise 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%2Fsplitwise.com%2Fsplitwise" | sh

Step 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%2Fsplitwise.com%2Fsplitwise" | 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 Splitwise API.

Get current user

Update user

List groups

Create group

Delete group

Use Cases

Patterns agents use Splitwise API for, with concrete tasks.

GET STARTED

Start building with Splitwise API

Explore with Jentic One

View OpenAPI Document

Automated Comments Management

Automate comments operations by combining multiple Splitwise API endpoints. Agents can get user and then update user in a single workflow.

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

AI Agent Integration via Jentic

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

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

Key Endpoints

27 endpoints — splitwise expense sharing api.

METHOD

PATH

DESCRIPTION

GET

/get_current_user

Get current user

GET

/get_user/{id}

Get user

POST

/update_user/{id}

Update user

GET

/get_groups

List groups

GET

/get_group/{id}

Get group

POST

/create_group

Create group

POST

/delete_group/{id}

Delete group

POST

/undelete_group/{id}

Restore group

GET

/get_current_user

Get current user

GET

/get_user/{id}

Get user

POST

/update_user/{id}

Update user

GET

/get_groups

List groups

GET

/get_group/{id}

Get group

POST

/create_group

Create group

POST

/delete_group/{id}

Delete group

POST

/undelete_group/{id}

Restore group

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Splitwise API by hand means choosing between its OAuth 2.0 authorization-code flow and API key auth, and pointing every call at the secure.splitwise.com/api/v3.0 host yourself. Through Jentic you install once, import the Splitwise API from the API Directory, store the credential once, and your agent calls it.

Permission scoping

Splitwise puts the group id in the URL path (/get_group/{id}, /delete_group/{id}), so a rule can pin your agent to reading one group. You choose the operations it may call, so destructive ones like deleting a group are not included unless you add them.

Credential isolation

Your Splitwise 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 'get the current user' or 'list my groups', and Jentic returns the matching Splitwise API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Splitwise API through Jentic.

What authentication does the Splitwise API use?

The Splitwise API uses apiKey, oauth2 authentication. 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 current user with the Splitwise API?

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

What are the rate limits for the Splitwise 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 current user through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get current user'. Jentic returns the matching Splitwise API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Splitwise API have?

The Splitwise API exposes 27 endpoints covering comments, expenses, friends operations.

Can I limit what my agent is allowed to do with the Splitwise API?

Yes. Because you self-host Jentic One, your own rules decide which Splitwise operations and credentials the agent may use. Since Splitwise puts the group id in the URL path, such as /get_group/{id} and /delete_group/{id}, you can pin the agent to reading a single group, and you choose which operations it can call so destructive ones like /delete_group/{id} are excluded unless you add them.

Splitwise API

Name: Splitwise API
Brand: Splitwise API
Availability: InStock

Official vendor OpenAPI document · agent-readyFinanceAccountingapiKey, oauth227 EndpointsREST

For Agents

Programmatically get current user, get user. Covers 27 operations with apiKey, oauth2 authentication.

Use for: I need to current user, I want to user, Search for user, Find all groups

Not supported: Does not handle payments, communications, or crm - use for finance and accounting only.

Splitwise expense sharing API. The API exposes 27 endpoints secured with apiKey, oauth2 authentication.

Jentic One on Github View OpenAPI Document

Connect the Splitwise API to your agent

Capabilities

Use Cases

Start building with Splitwise API

Key Endpoints

Why Jentic?

Related APIs

FAQs

Splitwise API