Waikit 1 Curfex API
Browse all Swaggerhub Waikit 1 APIsCommunity OpenAPI document · agent-readyCRMContact Managementbearer27 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Programmatically wallethistory, walletbalance. Covers 27 operations with bearer authentication.
Use for: I need to wallethistory, I want to walletbalance, Search for transferstatus, Find all transferreceipt
Not supported: Does not handle payments, communications, or developer tools - use for crm only.
Curfex integration API for business partner. This is a v2 version (released on 2022) replacing existing production version [Curfex API v1](https://app.swaggerhub.com/apis/curfex/curfex_api_v1). All listed APIs are [rate limited](https://www.notion.so/curfex/Rate-Limiting-def3bf1a33e345c4b34580ea282f3deb) Please contact us at tech@curfex.com if you need any help. The API exposes 27 endpoints secured with bearer authentication.
Install Jentic One Beta
Connect the Curfex API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Curfex 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.
1
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%2Fswaggerhub.waikit-1%2Fcurfex-api" | sh2
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%2Fswaggerhub.waikit-1%2Fcurfex-api" | 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.
Capabilities
What an agent can do with Curfex API.
walletHistory
walletBalance
transferStatus
transferReceipt
transferRate
transferInfoUpdate
transferHistory
Use Cases
Patterns agents use Curfex API for, with concrete tasks.
★ CRM Operations
Use the Curfex API to perform crm operations programmatically. The API provides 27 endpoints covering core functionality including wallethistory, walletbalance, transferstatus.
Call POST /api/walletHistory to wallethistory
Automated Event Subscription Management
Automate event subscription operations by combining multiple Curfex API endpoints. Agents can walletbalance and then transferstatus in a single workflow.
Call POST /api/walletBalance to walletbalance, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Curfex 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 'wallethistory', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
27 endpoints — curfex integration api for business partner.
METHOD
PATH
DESCRIPTION
POST
/api/walletHistory
walletHistory
POST
/api/walletBalance
walletBalance
POST
/api/transferStatus
transferStatus
POST
/api/transferReceipt
transferReceipt
POST
/api/transferRate
transferRate
POST
/api/transferInfoUpdate
transferInfoUpdate
POST
/api/transferHistory
transferHistory
POST
/api/transferBank
transferBank
POST
/api/walletHistory
walletHistory
POST
/api/walletBalance
walletBalance
POST
/api/transferStatus
transferStatus
POST
/api/transferReceipt
transferReceipt
POST
/api/transferRate
transferRate
POST
/api/transferInfoUpdate
transferInfoUpdate
POST
/api/transferHistory
transferHistory
POST
/api/transferBank
transferBank
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Curfex API by hand means acquiring a bearer token, attaching it to the Authorization header on every wallet and transfer call, and refreshing it yourself. Through Jentic you install once, import Curfex API from the API Directory, store the bearer token once, and your agent calls it.
Permission scoping
Curfex API sends its wallet and transfer targets in the request body rather than the URL path, so scope with operations-only language: limit the agent to the operations it needs, such as checking wallet balance or reading transfer history. You choose the operations it may call, so state-changing ones like updating transfer info are not included unless you add them.
Credential isolation
Your Curfex API bearer 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 'check wallet balance' or 'get transfer history', and Jentic returns the matching Curfex API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Curfex API through Jentic.
What authentication does the Curfex API use?
The Curfex 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 wallethistory with the Curfex API?
Yes. Use the POST /api/walletHistory endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Curfex 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 wallethistory through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'wallethistory'. Jentic returns the matching Curfex API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Curfex API have?
The Curfex API exposes 27 endpoints covering event subscription, authentication, enquiry operations.
Can I limit what my agent is allowed to do with the Curfex API?
Yes. Because Jentic One is self-hosted by you, your own rules decide which Curfex API operations and credentials the agent may use. Since Curfex sends its wallet and transfer targets in the request body rather than the URL path, you scope access at the operation level, allowing read-only calls like walletBalance, walletHistory, or transferHistory while withholding state-changing ones such as transferInfoUpdate. The agent can only call the operations you explicitly grant, and the stored bearer token is injected at execution time so it never reaches the agent's context.
GET STARTED