Install Jentic One Beta

Connect the SIM Swap (CAMARA) to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the SIM Swap (CAMARA), 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%2Fdeveloper.vodafone.com%2Fvodafone" | 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%2Fdeveloper.vodafone.com%2Fvodafone" | 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 SIM Swap (CAMARA) API.

Check whether a SIM was swapped within a configurable lookback window through POST /sim-swap/v1/check

Retrieve the exact date of the last SIM swap for a phone number via POST /sim-swap/v1/retrieve-date

Obtain access tokens through the JWT bearer grant on /oauth2/v2/token for backend-to-backend calls

Run the OpenID Connect CIBA flow with bc-authorize and token endpoints for user-consented checks

GET STARTED

Start building with SIM Swap (CAMARA) API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use SIM Swap (CAMARA) API for, with concrete tasks.

★ OTP fraud prevention before account takeover

Banks, fintechs, and payment platforms can call SIM Swap before delivering an SMS one-time password to confirm the SIM has not been swapped within a recent window. If the SIM was swapped recently the application can downgrade the channel to in-app push or step up to identity verification. The check returns a boolean within milliseconds and consumes one request per verification.

Call POST /sim-swap/v1/check with the phone number +447700900000 and a 240-hour window, then return whether the SIM was swapped.

Forensic timeline reconstruction

Fraud and investigations teams can call retrieve-date to get the exact timestamp of the last SIM swap for a phone number under investigation. Combined with internal session logs and KYC records this lets analysts confirm whether account takeover lined up with the SIM swap event. The API returns ISO-8601 timestamps and is intended for back-office investigations rather than real-time gating.

Call POST /sim-swap/v1/retrieve-date for phone number +447700900000 and return the latest swap timestamp for the investigations dashboard.

CIBA-consented verification for regulated workflows

For workflows that require explicit subscriber consent - such as PSD2 strong customer authentication or carrier-billing top-ups - the API exposes the OpenID Connect CIBA backchannel flow. The application calls bc-authorize, the subscriber consents on their device, then the application redeems the auth_req_id at the token endpoint to call the SIM swap check.

Run POST /openIDConnectCIBA/v1/bc-authorize for the subscriber, poll POST /openIDConnectCIBA/v1/token until the auth completes, then call /sim-swap/v1/check with the resulting access token.

Agent-driven anti-fraud checks via Jentic

AI agents handling login risk scoring or payment authorisation can call Vodafone SIM Swap through Jentic without juggling JWT signing or CIBA polling. Jentic stores the OAuth client secret in your Jentic One instance and abstracts the token exchange, so the agent only sees the simple intent of checking whether a SIM was swapped.

Search Jentic for 'check if a SIM was recently swapped', load the schema for /sim-swap/v1/check, and execute against +447700900000 with a 24-hour window.

Key Endpoints

6 endpoints — jentic publishes the only available openapi specification for sim swap (camara), keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/sim-swap/v1/check

Check if SIM was swapped within window

POST

/sim-swap/v1/retrieve-date

Get latest SIM swap date

POST

/oauth2/v2/token

Get access token using JWT bearer

POST

/openIDConnectCIBA/v1/bc-authorize

Initiate CIBA flow

POST

/openIDConnectCIBA/v1/token

Exchange CIBA auth_req_id for token

GET

/sim-swap/v1/ping

Sandbox health check

POST

/sim-swap/v1/check

Check if SIM was swapped within window

POST

/sim-swap/v1/retrieve-date

Get latest SIM swap date

POST

/oauth2/v2/token

Get access token using JWT bearer

POST

/openIDConnectCIBA/v1/bc-authorize

Initiate CIBA flow

POST

/openIDConnectCIBA/v1/token

Exchange CIBA auth_req_id for token

GET

/sim-swap/v1/ping

Sandbox health check

Why Jentic?

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

Setup

Wiring the Vodafone SIM Swap API by hand means running the OAuth2 and CIBA back-channel flows, choosing the sandbox or production host, and minting a fresh access token per call yourself. Through Jentic you install once, import the SIM Swap API from the API Directory, store the client credentials once, and your agent calls it.

Permission scoping

You choose which SIM Swap operations the agent may call, so you can limit it to the ones it needs, such as checking whether a SIM was recently swapped, and leave the swap-date retrieval out unless you add it. The API only reports on SIM-swap events, so the agent cannot send SMS or verify identity documents.

Credential isolation

Your Vodafone client secret and signing key 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 'check if a SIM was recently swapped', and Jentic returns the matching SIM Swap operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using SIM Swap (CAMARA) API through Jentic.

Why is there no official OpenAPI spec for SIM Swap (CAMARA)?

Vodafone does not publish an OpenAPI specification for this CAMARA SIM Swap endpoint. Jentic generates and maintains this spec so that AI agents and developers can call SIM Swap (CAMARA) via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Vodafone SIM Swap API use?

The API uses OAuth 2.0 with two flows: a JWT bearer assertion grant on POST /oauth2/v2/token for backend-to-backend access, and OpenID Connect CIBA via /openIDConnectCIBA/v1/bc-authorize for user-consented checks. Through Jentic, the client secret is held in your Jentic One instance and tokens are minted per call.

Can I detect SIM-swap fraud with the Vodafone SIM Swap API?

Yes. POST /sim-swap/v1/check returns whether the SIM was swapped within the supplied lookback window, and POST /sim-swap/v1/retrieve-date returns the latest swap timestamp. Use the boolean check inline in OTP and login flows and the date endpoint for forensic review.

What are the rate limits for the Vodafone SIM Swap API?

Limits are not declared in the OpenAPI spec and Vodafone applies tenant-specific limits agreed during commercial onboarding. The sandbox is rate-limited more aggressively than production. Test with backoff on 429 responses and confirm production limits with your Vodafone account manager.

How do I check a SIM swap through Jentic?

Run pip install jentic, then with the async client search for 'check if a SIM was recently swapped', load the schema for POST /sim-swap/v1/check, and execute with the phone number and a maxAge window. Jentic returns the boolean swap result.

Is the Vodafone SIM Swap API a CAMARA-compliant endpoint?

Yes. The endpoint paths and request/response shapes follow the GSMA CAMARA SIM Swap specification, so an integration written against this API can be portable across other CAMARA-aligned operators with minor base URL changes.

Can I limit what my agent is allowed to do with the Vodafone SIM Swap API?

Yes. Jentic One is self-hosted by you, so your own rules decide which SIM Swap operations and credentials the agent may use. You can allow only POST /sim-swap/v1/check so the agent confirms whether a SIM was recently swapped, and leave out POST /sim-swap/v1/retrieve-date unless you choose to add it. Because the API only reports SIM-swap events, the agent cannot send SMS or verify identity documents.

Vodafone SIM Swap (CAMARA)

AI ReadinessAI-Aware (B+)67/100

See full scorecard

Agent-ready OpenAPI document · curated by JenticIdentity AuthIdentity Verificationoauth26 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Verify whether a mobile number's SIM was recently swapped to harden SMS-OTP, login, and high-value transaction flows against SIM-swap fraud.

Use for: I need to verify whether the customer's SIM was swapped in the last 240 hours before sending a high-value transfer, Check whether a phone number had a recent SIM swap before approving an OTP login, Retrieve the exact date of the last SIM swap for a flagged account, Get an OAuth access token using the JWT bearer flow

Not supported: Does not handle sending SMS, identity document verification, or call routing - use for SIM-swap fraud detection only.

Jentic publishes the only available OpenAPI specification for SIM Swap (CAMARA), keeping it validated and agent-ready. Vodafone's SIM Swap API implements the GSMA CAMARA standard for verifying that a subscriber's SIM card has not been recently swapped, a key signal in fraud detection for SMS one-time-password and account-recovery flows. The spec covers JWT and CIBA OAuth flows, a check endpoint that returns whether a SIM has been swapped within a window, a retrieve-date endpoint, and a health ping for sandbox monitoring.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

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

42%

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: A-Signals: 4

45%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

67%

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

61%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

83%

OperationId Quality

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

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.

100

Security

Trust, risk posture, and security compliance.

Grade: A+Signals: 1

100%

Authentication Strength

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

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the SIM Swap (CAMARA) to your agent

Capabilities

Start building with SIM Swap (CAMARA) API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Vodafone SIM Swap (CAMARA)

Jentic AI Readiness Score

SIM Swap (CAMARA)

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