Your conflict-of-interest networks. Open one to explore the map, or start a new run.
Depth234
Monitoring & alerts
Re-run a watchlist on a schedule and get alerted when the network changes.
Watchlist
Frequency
Last run
Next run
Alert when
Delivery
Status
Fund I counterparties
Weekly
2 Sep
9 Sep
New conflict ≥ 0.80
Email, webhook
Active
Portfolio boards
Daily
2 Sep
3 Sep
New sanctions / PEP hit
Email
Active
Advisor panel
Monthly
1 Sep
1 Oct
Any new connection
Slack
Active
Prototype view. A schedule runs the same engine as a workflow and compares each run against the previous result.
API
Native REST API for submitting workflows and retrieving results. Webhooks for run completion and alerts.
API key
mk_live_9c2f7a1b4e8d3f60a2c5e93f
Base URL https://api.sekhmetanalytics.com/v1
Submit a workflow
POST /v1/workflows
Authorization: Bearer mk_live_...
{
"name": "Fund I pre-drawdown",
"subjects": ["Jane Roe", "Acme Holdings Ltd"],
"universe": ["Portfolio Co A", "Counterparty B"],
"depth": 3
}
Check status and fetch findings
GET /v1/workflows/{id} -> { "status": "complete" }
GET /v1/workflows/{id}/findings -> [ { subject, universe, path, confidence, band } ]
GET /v1/workflows/{id}/graph -> { parties, connections }
Register a webhook to be notified on completion and on monitoring alerts.
Authentication
Send your key as a bearer token on every request. Keys carry scopes (workflows:read, workflows:write, findings:read). Use a test key (mk_test_...) against the sandbox.
# Python
from sekhmet import Meridian
m = Meridian(api_key="mk_live_...")
wf = m.workflows.create(name="Fund I", subjects=[...], universe=[...], depth=3)
print(wf.wait().findings)
// JavaScript
import { Meridian } from "@sekhmet/meridian";
const m = new Meridian("mk_live_...");
const wf = await m.workflows.create({ name: "Fund I", subjects: [...], universe: [...], depth: 3 });
console.log((await wf.wait()).findings);
Rate limits and pagination
Rate limit600 requests / minute per key
PaginationCursor via ?after=, up to 200 per page
ErrorsStandard HTTP status codes with a JSON error body
Guide
How Meridian works and how to use it.
What it does
Meridian maps the ownership, control and family connections around the parties you check, resolves records that refer to the same individual across sources, and flags where a party connects into your own universe. Every finding shows its evidence and a confidence value.
Reading the map
Red is the party under review; blue is a person; green is a company. Solid lines are connections; amber dashed lines are inferred kinship. Click any party or connection to see the evidence behind it.
Running a workflow
Open Workflows, choose New workflow, paste your watchlist and the universe to check it against, pick a depth, and submit. You are notified when the run completes; results open as the map with a findings list and a CSV export.
Monitoring and API
Set a watchlist to re-run on a schedule with alerts under Monitoring, or drive the same steps programmatically through the API.
Settings
Workspace, sources and team.
Workspace
Sources
Companies House (UK)On
SEC EDGAROn
OpenSanctionsOn
ICIJ Offshore LeaksOn
NorthData (paid)Add-on
Team
demo@sekhmetanalytics.comOwner
Invite a teammate
New workflow
Define the parties to check and the universe to check them against.
SekhmetMeridian