EmailValidation SDK

Kiprio API client, generated from the OpenAPI spec.

30+ utility APIs for domain intelligence, email validation, SSL inspection, image generation, content processing, and more.

Learn more about Kiprio API at kiprio.com/docs.

This is an unofficial SDK for the Kiprio public API, generated by Voxgig with @voxgig/sdkgen. It is not affiliated with, endorsed by, or sponsored by the upstream API provider.

Learn more about Voxgig SDKs at voxgig.com/sdk.

Metadata kindly supplied by www.freepublicapis.com.

TypeScript, Python, PHP, Golang, Ruby, Lua SDKs, a CLI, an interactive REPL, and an MCP server for AI agents — all generated from one OpenAPI spec by @voxgig/sdkgen.

Entities, not endpoints

This SDK exposes the API as 10 semantic entities that you call directly, instead of assembling URL paths and query strings. See the Entities table below for the full list. Entities are Capitalised to mark them as the primary surface, each with the operations they support (list, load, create):

const client = new EmailValidationSDK()
const dnsresult = await client.DnsResult().load()

Thinking in entities keeps the mental model small — for people and AI agents alike — rather than reasoning about raw HTTP routes and query parameters.

Offline unit testing

Every SDK ships a built-in test mode that swaps the HTTP transport for an in-memory mock, so your unit tests run fully offline — no server, no network, and no credentials:

TypeScript

const client = EmailValidationSDK.test()
const dnsresult = await client.DnsResult().load()
// dnsresult is a bare DnsResult populated with mock data
console.log(dnsresult)

Python

client = EmailValidationSDK.test()
dnsresult = client.DnsResult().load()
print(dnsresult)

PHP

// Seed fixture data so offline calls resolve without a live server.
$client = EmailValidationSDK::test([
    "entity" => ["dnsresult" => ["test01" => []]],
]);
$dnsresult = $client->DnsResult()->load();

Golang

client := sdk.Test()
result, err := client.DnsResult(nil).Load(
    nil, nil,
)

Ruby

# Seed fixture data so offline calls resolve without a live server.
client = EmailValidationSDK.test({
  "entity" => { "dnsresult" => { "test01" => {} } },
})
dnsresult = client.DnsResult.load()

Lua

local client = sdk.test()
local result, err = client:DnsResult():load()

Packages

Language	Package	Install
TypeScript	@voxgig-sdk/email-validation	publish pending — install from git tag
Python	voxgig-sdk-email-validation	publish pending — install from git tag
PHP	voxgig-sdk/email-validation	publish pending — install from git tag
Golang	github.com/voxgig-sdk/email-validation-sdk/go	go get github.com/voxgig-sdk/email-validation-sdk/go@latest
Ruby	voxgig-sdk-email-validation	publish pending — install from git tag
Lua	voxgig-sdk-email-validation	publish pending — install from git tag
Go CLI	github.com/voxgig-sdk/email-validation-sdk/go-cli	go install github.com/voxgig-sdk/email-validation-sdk/go-cli/cmd/email-validation@latest
Go MCP server	github.com/voxgig-sdk/email-validation-sdk/go-mcp	go get github.com/voxgig-sdk/email-validation-sdk/go-mcp@latest

Quickstart

TypeScript

import { EmailValidationSDK } from '@voxgig-sdk/email-validation'

const client = new EmailValidationSDK({
  apikey: process.env.EMAIL_VALIDATION_APIKEY,
})

// Load dnsresult data (returns a DnsResult)
const dnsresult = await client.DnsResult().load()
console.log(dnsresult)

See the TypeScript README for the full guide.

Surfaces

Surface	Path
SDK (TypeScript, Python, PHP, Golang, Ruby, Lua)	ts/ py/ php/ go/ rb/ lua/
CLI	go-cli/
MCP server	go-mcp/

Use it from an AI agent (MCP)

The generated MCP server exposes every operation in this SDK as an MCP tool that Claude, Cursor or Cline can call directly. Build and register it:

cd go-mcp && go build -o email-validation-mcp .

Then add it to your agent's MCP config (Claude Desktop, Cursor, etc.):

{
  "mcpServers": {
    "email-validation": {
      "command": "/abs/path/to/email-validation-mcp"
    }
  }
}

Entities

The API exposes 10 entities:

Entity	Description	API path
DnsResult	The DnsResult entity (load).	/dns-lookup
Domain	The Domain entity (list).	/robots-txt
EmailValidate	The EmailValidate entity (load).	/email-validate
Generate	The Generate entity (load).	/qr
Grammar	The Grammar entity (create).	/grammar
Ipn	The Ipn entity (load).	/ip
Redact	The Redact entity (create).	/redact
Ssl	The Ssl entity (list).	/ssl
Utility	The Utility entity (load).	/hash
Whoi	The Whoi entity (list).	/whois

The operations available across these entities are load, list, create — see each entity's own list above for exactly which it supports.

Quickstart in other languages

Python

import os
from emailvalidation_sdk import EmailValidationSDK

client = EmailValidationSDK({
    "apikey": os.environ.get("EMAIL_VALIDATION_APIKEY"),
})


# Load a specific dnsresult (returns the record, raises on error)
dnsresult = client.DnsResult().load()
print(dnsresult)

PHP

<?php
require_once 'emailvalidation_sdk.php';

$client = new EmailValidationSDK([
    "apikey" => getenv("EMAIL_VALIDATION_APIKEY"),
]);


// Load a specific dnsresult (returns the bare record; throws on error)
$dnsresult = $client->DnsResult()->load();
print_r($dnsresult);

Golang

import sdk "github.com/voxgig-sdk/email-validation-sdk/go"

client := sdk.NewEmailValidationSDK(map[string]any{
    "apikey": os.Getenv("EMAIL_VALIDATION_APIKEY"),
})

// Load dnsresult data
dnsResult, err := client.DnsResult(nil).Load(nil, nil)
if err != nil {
    panic(err)
}
fmt.Println(dnsResult)

Ruby

require_relative "EmailValidation_sdk"

client = EmailValidationSDK.new({
  "apikey" => ENV["EMAIL_VALIDATION_APIKEY"],
})


# Load a specific dnsresult (returns the bare record; raises on error)
dnsresult = client.DnsResult.load()
puts dnsresult

Lua

local sdk = require("email-validation_sdk")

local client = sdk.new({
  apikey = os.getenv("EMAIL_VALIDATION_APIKEY"),
})


-- Load a specific dnsresult
local dnsresult, err = client:DnsResult():load()
print(dnsresult)

Direct and prepare

For endpoints the entity model doesn't cover, use the low-level methods:

• direct(fetchargs) — build and send an HTTP request in one step.
• prepare(fetchargs) — build the request without sending it.

Both accept a map with path, method, params, query, headers, and body. See the How-to guides below.

How-to guides

Make a direct API call

When the entity interface does not cover an endpoint, use direct:

TypeScript:

const result = await client.direct({
  path: '/api/resource/{id}',
  method: 'GET',
  params: { id: 'example' },
})
if (result instanceof Error) {
  throw result
}
console.log(result.data)

Python:

result = client.direct({
    "path": "/api/resource/{id}",
    "method": "GET",
    "params": {"id": "example"},
})

PHP:

$result = $client->direct([
    "path" => "/api/resource/{id}",
    "method" => "GET",
    "params" => ["id" => "example"],
]);

Go:

result, err := client.Direct(map[string]any{
    "path":   "/api/resource/{id}",
    "method": "GET",
    "params": map[string]any{"id": "example"},
})
if err != nil {
    panic(err)
}
fmt.Println(result)

Ruby:

result = client.direct({
  "path" => "/api/resource/{id}",
  "method" => "GET",
  "params" => { "id" => "example" },
})

Lua:

local result, err = client:direct({
  path = "/api/resource/{id}",
  method = "GET",
  params = { id = "example" },
})

Advanced

Everyday use only needs the sections above. This explains the internals behind every call — relevant when writing custom features.

Every SDK call runs the same five-stage pipeline:

1. Point — resolve the API endpoint from the operation definition.
2. Spec — build the HTTP specification (URL, method, headers, body).
3. Request — send the HTTP request.
4. Response — receive and parse the response.
5. Result — extract the result data for the caller.

A feature hook fires at each stage (e.g. PrePoint, PreSpec, PreRequest), so features can inspect or modify the pipeline without forking the SDK.

Features

Feature	Purpose
TestFeature	In-memory mock transport for testing without a live server

Pass custom features via the extend option at construction time.

Per-language documentation

• TypeScript
• Python
• PHP
• Golang
• Ruby
• Lua

Upstream API

This SDK is generated from the upstream OpenAPI specification. It is an unofficial client and is not affiliated with the API provider.

• Upstream API: https://kiprio.com

Security

Please report security issues to security@voxgig.com. See SECURITY.md. Do not open public issues for suspected vulnerabilities.

---

Generated from the Kiprio API OpenAPI spec by @voxgig/sdkgen.