Skip to API documentation

AEGLIX MIND

Connected intelligence.Security research, connected

AEGLIX MIND / DEVELOPER PLATFORM v1

Security intelligence, in your workflow.

Analyze suspicious URLs, messages and screenshot text. Connect public-source evidence and vulnerability context to your own applications.

From a key to your first assessment

  1. Sign in and request a premium API plan using your account email.
  2. After activation, open the API console and create a key. Choose only the permissions your app needs.
  3. Save the key once in your backend’s secret manager. Send it as a Bearer token over HTTPS.
  4. Submit content with explicit consent. Use the result and its limitations to drive your review or flagging workflow.

Base URL: https://aeglixmind.com/api/v1/integrations. Call from your server. Never embed a key in frontend JavaScript, a mobile app bundle, a URL or a public repository.

curl https://aeglixmind.com/api/v1/integrations/guardian/analyze \
  -H "Authorization: Bearer $AEGLIX_API_KEY" \
  -H 'Content-Type: application/json' \
  --data '{"kind":"url","url":"example.com","consent":true}'

Five focused operations

OperationPermissionReturns
POST /guardian/analyzeguardian:writeURL, message or screenshot text assessment
GET /guardian/analyses/{id}guardian:readAn unexpired assessment created by that key
POST /intelligence/lookupintelligence:readBounded public feed evidence and entity IDs
GET /entities/{id}/relationshipsrelationships:readPublic feed relationships, sources and retrieval dates
GET /cves/{cve_id}cves:readIndexed NVD vulnerability and CISA context

Suffixes above follow the base URL. Requests and responses use JSON. Campaigns and Arsenal are not included in this API.

Analysis inputs

Choose exactly one kind and content field. consent must be the JSON boolean true.

{"kind":"url","url":"https://example.com/path","deep_scan":false,"consent":true}
{"kind":"message","text":"An unexpected message asking for a money transfer.","consent":true}
{"kind":"screenshot","image_base64":"BASE64_IMAGE_BYTES","consent":true}

Messages: 10–12,000 characters. Screenshots: still PNG/JPEG/WebP up to 4 MiB and 12 megapixels, standard base64 without a data URI prefix. Total JSON body: at most 6 MiB. deep_scan:true opts into bounded URL content fetching. URLs in message or screenshot text are not separately scanned.

Responses and stored intelligence

A completed analysis uses schema_version: guardian-assessment-v1 and returns id, kind, status, created_at, expires_at and result. URL results include risk level, factors, explanation, ML/model analysis and unavailable providers. Message results include verdict, summary, warning signs, recommended actions and limitations. Score and confidence are not safety guarantees.

Lookup body: {"kind":"domain","value":"example.com"}. Kinds: domain, url, ip, hash and cve. Hashes use sha256:HEX, sha1:HEX or md5:HEX. An empty result means unknown, not safe. Public relationships are source-reported, not independent confirmations or actor attribution. Indexed CVE reads do not fetch new NVD records on demand.

Provider coverage can be incomplete. A URL analysis may complete with unavailable providers or model augmentation; inspect those fields before taking action.

Build on your backend

Node.js / server-side fetch
const response = await fetch(
  'https://aeglixmind.com/api/v1/integrations/guardian/analyze', {
    method: 'POST',
    headers: {
      Authorization: `Bearer ${process.env.AEGLIX_API_KEY}`,
      'Content-Type': 'application/json'
    },
    body: JSON.stringify({kind: 'message', text: message, consent: true}),
    signal: AbortSignal.timeout(185000)
  });
if (!response.ok) throw new Error(`AEGLIX API: ${response.status}`);
const assessment = await response.json();
Python / requests
import os
import requests

response = requests.post(
    'https://aeglixmind.com/api/v1/integrations/guardian/analyze',
    headers={'Authorization': f'Bearer {os.environ["AEGLIX_API_KEY"]}'},
    json={'kind': 'url', 'url': 'example.com', 'consent': True},
    timeout=(10, 185),
)
response.raise_for_status()
assessment = response.json()

Use GET /guardian/analyses/{id} with the same key to retrieve a completed result. Store assessment IDs in your system; identifiers do not grant access without the creating key.

Predictable limits and failure handling

Daily allowance is volume, not simultaneous processing capacity. Analysis runs synchronously, with a 180-second application deadline and bounded shared capacity. Start with one or two requests in flight and increase only after observing latency and capacity responses. Higher daily allowances do not promise reserved concurrency or a response-time SLA.

Admitted responses expose X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset (UTC epoch seconds), and X-RateLimit-Key-Remaining. Your per-key cap can be lower than the shared plan allowance.

StatusWhat to do
401Check the key, expiry and revocation status.
403Check the required permission and active premium plan.
404Record unavailable, expired or inaccessible to this key. It is not a clean verdict.
413 / 415 / 422Fix input size, JSON content type, consent or field values before retrying.
429Daily or per-minute allowance reached. Respect Retry-After.
503Capacity or provider unavailable. Back off using Retry-After with jitter.

Errors include a stable error.code, a readable message and a support request_id, also returned as X-Request-ID. Keep the request ID for support; never log key secrets or private submissions.

There is no queue, bulk endpoint, webhook or idempotency guarantee in this release. A timed-out or retried POST may consume another request and create another assessment. Do not retry blindly. Client or reverse proxy timeouts can be shorter than the application deadline.

Room to build. Clear daily allowances.

Premium API access. Contact us for pricing and activation; no payment is taken on this page.

Starter

500 requests / day

Up to 30 requests per minute

Five active keys · scoped permissions · usage dashboard

Request Starter

Growth

2,500 requests / day

Up to 60 requests per minute

Five active keys · scoped permissions · usage dashboard

Request Growth

Scale

10,000 requests / day

Up to 120 requests per minute

Five active keys · scoped permissions · usage dashboard

Request Scale

Allowances are shared across every key in your account and reset at 00:00 UTC. Creating or rotating keys does not add requests. Need a larger allowance? Discuss custom capacity.

One admitted API call uses one request, including result reads, invalid submissions, missing records and upstream failures. Authentication failures, denied scopes and rejected quota/rate admissions do not use requests. Key management and viewing console usage do not consume your integration allowance. No automatic overage charges.

Handle submissions and results as private data

Only submit content you are authorized to process. Consent permits the configured external threat/model services to process it. Redact personal data and credentials first. Screenshot OCR runs locally, then sends extracted text for model analysis immediately; use reviewed message text if you need a redaction step.

Assessment retrieval expires after seven days and is restricted to the creating key. Revoking a key also prevents retrieval of its prior assessments; export needed results before a planned rotation. URL scans also enter the account’s Guardian history under its separate retention rules. Original messages, images and OCR text are not saved separately, but generated results may contain excerpts. See the privacy policy and terms of use.

Need help activating or changing an allowance? Contact API support with your account email and key ID, never the key secret or unredacted submissions.