Install Jentic One Beta

Connect the net2phone API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the net2phone 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%2Fn2p.io%2Fn2p" | 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%2Fn2p.io%2Fn2p" | 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 net2phone API.

Place an outbound call to an E.164 number, extension, or SIP address from a user, with optional auto_answer on Gen V accounts

Pull call data records for the current user, a specific user by userId, or all users on the account

Subscribe a post_uri to calls, cdrs, and recordings events for one user or all users, with an expires_in lifetime

Check or delete a webhook subscription by subscriptionId

GET STARTED

Start building with net2phone API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use net2phone API for, with concrete tasks.

★ Agent click-to-call through Jentic

A developer's sales agent, connected through Jentic, places a call when a lead asks to be phoned back. It calls the place-call operation with the lead's number in E.164 format as to, and the rep's user as from, so the call starts from the rep's own net2phone line without anyone dialling by hand.

Call POST /calls/ with to='+14155550123' and from set to the authenticated user's id from GET /users/current/

Call activity reporting

A manager wants a summary of the team's call activity. An agent pulls call data records for each user from the per-user CDR endpoint, reads start_time, end_time, duration, call_type, and the from and to legs, and builds a per-rep report. On Gen V accounts the all-users CDR listing returns records for everyone in one call.

Call GET /users/ to list users, then GET /cdrs/users/{userId}/ for each one and total the call count per user

Real-time call and recording events

A CRM integration needs to log calls as they happen. A webhook subscription with calls, cdrs, or recordings set to true posts each event to your post_uri, scoped to one user or all users. Subscriptions expire after expires_in seconds, up to 604800, so the integration checks and renews them on a schedule.

Call POST /subscriptions/ with post_uri='https://hooks.example.com/n2p', calls=true, cdrs=true, and expires_in=604800, then GET /subscriptions/{subscriptionId}/ to confirm it

Key Endpoints

12 endpoints — the net2phone api places outbound calls from a net2phone user or device, returns call data records for the current user or any user on the account, and manages webhook subscriptions for call, cdr, and recording events.

METHOD

PATH

DESCRIPTION

POST

/calls/

Place a call

GET

/cdrs/users/current/

Current user CDRs

GET

/cdrs/users/{userId}/

User CDRs by ID

POST

/subscriptions/

Create a webhook subscription

DELETE

/subscriptions/{subscriptionId}/

Delete a webhook subscription

GET

/users/

List users on the account

POST

/calls/

Place a call

GET

/cdrs/users/current/

Current user CDRs

GET

/cdrs/users/{userId}/

User CDRs by ID

POST

/subscriptions/

Create a webhook subscription

DELETE

/subscriptions/{subscriptionId}/

Delete a webhook subscription

GET

/users/

List users on the account

Why Jentic?

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

Setup

Wiring net2phone by hand means running the OAuth password flow against its token URL, refreshing tokens, sending the versioned media type the API expects, and working out which from format your account generation takes. Through Jentic you install once, import net2phone from the API Directory, store the credentials once, and your agent calls it.

Permission scoping

net2phone puts the user id in the URL path of the per-user CDR and user endpoints, so a rule can pin your agent to specific users' records. You choose the operations it may call, so actions like placing calls or deleting a webhook subscription are not included unless you add them.

Credential isolation

Your net2phone credentials and access token are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'place a phone call' or 'list my call records', and Jentic returns the matching net2phone operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using net2phone API through Jentic.

What authentication does the net2phone API use?

Per its OpenAPI spec, the net2phone API uses OAuth 2.0 with the password flow: you exchange your net2phone credentials for an access token at the /oauth/token/ endpoint on api.n2p.io and send it with each call. Through Jentic, the credentials and token are stored once by your own Jentic One instance and injected at call time.

What can I put in the to and from fields when placing a call?

POST /calls/ requires to, which can be a phone number, an extension, or a SIP address; E.164 is recommended for numbers. The from field depends on account generation: Gen P and Gen V take the authenticated user id, Gen U and Gen X take the user's phone number or extension, and Gen V also accepts a SIP user.

What are the rate limits for the net2phone API?

The spec documents an x-RateLimit-Limit response header per endpoint, with values such as 5/second, 15/minute on the user CDR listing, and some endpoints document 1/second limits. Exceeding a limit returns HTTP 429.

How long does a net2phone webhook subscription last?

Subscriptions expire after expires_in seconds, which defaults to 7200 and can be set up to 604800. Set calls, cdrs, or recordings to true to choose event types, and leave user at its default of * to cover all users. GET /subscriptions/{subscriptionId}/ verifies a subscription, and DELETE removes it.

How do I place a call through net2phone with Jentic?

Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, import the net2phone API from the API Directory, and store your net2phone credentials once. Your agent searches for 'place a phone call', gets the call operation with its input schema, and calls POST /calls/ with a to number. To run it on your own infrastructure, install Jentic One from its GitHub repo.

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

Yes. For a reporting agent, write a rule that allows only GET /cdrs/users/{userId}/ for the user ids it should read, so it can pull call records for those people but cannot place calls or change webhook subscriptions. Add POST /calls/ only for an agent that should dial out.

N2p net2phone API

AI ReadinessFoundational (D)43/100

See full scorecard

Official vendor OpenAPI document · agent-readyCommunicationsVoice Telephonyoauth212 EndpointsREST

For Agents

Place click-to-call phone calls from a net2phone user, pull call data records per user, and subscribe a URL to call, CDR, and recording events.

Use for: Place a call from my net2phone line to +14155550123, List my call records from net2phone, Retrieve the call data records for a teammate's extension, Set up a webhook that fires on new call events

Not supported: Does not send SMS, manage phone numbers, or download call recordings. Use for net2phone click-to-call, call data records, and event webhooks only.

The net2phone API places outbound calls from a net2phone user or device, returns call data records for the current user or any user on the account, and manages webhook subscriptions for call, CDR, and recording events. It also returns the authenticated user, the account, and the list of users. A call takes a to value as an E.164 number, extension, or SIP address and an optional from, whose accepted form depends on the account generation. Webhook subscriptions post to a post_uri you supply and expire after expires_in seconds.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

88%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: BSignals: 4

11%

Example Density

How richly the API is illustrated with examples.

76%

Example Validity

Percentage of examples that conform to their schemas.

75%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4

67%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

31%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1

30%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: DSignals: 1

46%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the net2phone API to your agent

Capabilities

Start building with net2phone API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

N2p net2phone API

Jentic AI Readiness Score

net2phone API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness