Install Jentic One Beta

Connect the Interzoid Get Full Name Parsed Match Similarity Key API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Interzoid Get Full Name Parsed Match Similarity Key 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%2Finterzoid.com%2Finterzoid-get-full-name-parsed-match-similarity-ke" | 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%2Finterzoid.com%2Finterzoid-get-full-name-parsed-match-similarity-ke" | 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 Interzoid Get Full Name Parsed Match Similarity Key API.

Generate a deterministic similarity key from separate first-name and last-name inputs

Collapse contact records that store the same person under spelling variants in either field

Join two contact lists on parsed name components by hashing both sides to a similarity key

Cluster engagement events by person despite typos in either name field

GET STARTED

Start building with Interzoid Get Full Name Parsed Match Similarity Key API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Interzoid Get Full Name Parsed Match Similarity Key API for, with concrete tasks.

★ Contact dedup with parsed name fields

CRMs that store given and family name in separate columns call the Interzoid Get Full Name Parsed Match Similarity Key API for each contact and group rows by the returned key. Variants like 'Jon'/'Smith' and 'John'/'Smyth' typically collapse to one cluster, so reps no longer call the same person twice from differently-spelled records.

Iterate the contacts table, call /getfullnameparsedmatch with firstname and lastname set to the row's values, and group by the returned key.

B2B lead-list cross-reference on parsed names

When a B2B lead list lands with first and last name pre-parsed, marketing computes the Interzoid parsed-name similarity key on both the inbound list and the existing CRM and joins on the key. The fuzzy join captures matches that exact-string compare misses across both name fields.

Compute /getfullnameparsedmatch keys for the firstname and lastname columns in both the inbound list and the existing CRM, then suppress leads whose key already exists.

MDM contact-name normalization

Master data management pipelines call the Interzoid Get Full Name Parsed Match Similarity Key API on every customer record at ingest to attach a stable person cluster ID. Reporting layers aggregate engagement and revenue by cluster ID rather than raw name strings, removing duplicate-name distortion in dashboards.

On every insert into the contacts staging table, call /getfullnameparsedmatch and persist the returned key as person_match_key for downstream BI.

AI agent parsed-name dedup

An AI agent assisting an analyst with a contact cleanup discovers the Interzoid Get Full Name Parsed Match Similarity Key API through Jentic and uses it to flag near-duplicates when the dataset has parsed first and last names. Jentic stores the Interzoid license key in the credential vault and injects it as the license query parameter at execution time, so the agent never sees the raw key.

Search Jentic for 'similarity key for parsed first and last name', load the Interzoid Get Full Name Parsed Match operation, and execute it for each contact's firstname and lastname pair.

Key Endpoints

1 endpoints — the interzoid get full name parsed match similarity key api returns an algorithmic similarity key for a person's name when first and last name are stored in separate fields.

METHOD

PATH

DESCRIPTION

GET

/getfullnameparsedmatch

Return a similarity key for parsed first and last name inputs

GET

/getfullnameparsedmatch

Return a similarity key for parsed first and last name inputs

Why Jentic?

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

Setup

Wiring the Interzoid Get Full Name Parsed Match Similarity Key API by hand means obtaining a license key, appending it as a license query parameter on each call to /getfullnameparsedmatch, and handling the request plumbing yourself. Through Jentic you install once, import this API from the API Directory, store the license key once, and your agent calls it.

Permission scoping

This API exposes a single read-only GET /getfullnameparsedmatch operation that takes parsed first and last name fields in the query, with no resource id in the URL path, so scoping is at the operation level: you limit the agent to the similarity-key lookup it needs. It only computes a match key and writes nothing, so there is no destructive operation to include.

Credential isolation

Your Interzoid license key is stored once, encrypted, by your own Jentic One instance and injected as the license parameter at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'similarity key for parsed first and last name', and Jentic returns the Get Full Name Parsed Match operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Interzoid Get Full Name Parsed Match Similarity Key API through Jentic.

What authentication does the Interzoid Get Full Name Parsed Match Similarity Key API use?

The API uses a license key passed as the license query parameter on every call to /getfullnameparsedmatch. Through Jentic the license key is held in the credential vault and injected at execution time, so the agent never handles the raw key.

What if my data stores the full name in a single field instead of separate first and last name columns?

Use the Interzoid Get Full Name Match Similarity Key API instead - it accepts the combined name as a single fullname parameter. The /getfullnameparsedmatch endpoint expects firstname and lastname to be passed separately.

What are the rate limits for the Interzoid Get Full Name Parsed Match Similarity Key API?

The OpenAPI spec does not publish a numeric rate limit. Interzoid enforces per-license-tier quotas on the account dashboard, so check your account before running batch dedup jobs.

How do I deduplicate parsed name fields through Jentic?

Install the SDK with pip install jentic, search for 'similarity key for parsed first and last name', load the Interzoid Get Full Name Parsed Match operation, and execute it for each row's firstname and lastname pair.

Does the API handle middle names or initials?

The endpoint operates on firstname and lastname inputs. Middle names and initials are typically dropped or appended to the first name in calling code before the API is invoked, so the similarity key reflects the primary given and family names.

Can I limit what my agent is allowed to do with the Interzoid Get Full Name Parsed Match Similarity Key API?

Yes. Because you self-host Jentic One, your own rules decide which operations and credentials the agent may use, and this API exposes only a single read-only GET operation that computes a name-match similarity key. You can scope the agent to just that similarity-key lookup, and since there is no resource id in the path and the operation writes nothing, the agent can only read match keys, never modify data.

Interzoid Get Full Name Parsed Match Similarity Key API

Name: Interzoid Get Full Name Parsed Match Similarity Key API
Brand: Interzoid Get Full Name Parsed Match Similarity Key API
Availability: InStock

Browse all Interzoid APIs

Community OpenAPI document · agent-readyData EnrichmentData TransformationapiKey1 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Generate a similarity key for a person's name when first and last name are in separate fields. One GET endpoint, license-key auth.

Use for: Generate a similarity key from firstname=John lastname=Smith, Match 'Jon Smyth' and 'John Smith' as the same person, Deduplicate a contacts table on first and last name columns, Get a fuzzy match key for parsed person name fields

Not supported: Does not enrich contacts with demographics, validate that a person exists, or combine first and last name back into a single string - use for fuzzy-match key generation on parsed first and last name inputs only.

The Interzoid Get Full Name Parsed Match Similarity Key API returns an algorithmic similarity key for a person's name when first and last name are stored in separate fields. Variants such as 'John' / 'Smith' and 'Jon' / 'Smyth' typically produce the same key, so deduplication and contact-merging jobs can join on the key without recombining the components first. The single GET /getfullnameparsedmatch endpoint authenticates with a license key passed as a query parameter and returns the similarity key as JSON. Use the Full Name Similarity Key API when the name lives in a single field.

Jentic One on Github View OpenAPI Document