GIGyftPro EnterpriseGyftPro IntelligenceRelationship-aware gifting intelligence
Developers and technical evaluators

A credible API surface with operational context attached.

The technical story is intentionally clean: additive versioning, reliability metadata, partner-safe endpoints, and a portal layer for usage, quota, invoicing, and key management.

Current external endpoints
  • GET /v1/gifting-trends
  • POST /v1/gift-recommendations
  • POST /v1/gifting-intent
  • POST /v1/occasion-predictions
  • GET /v1/gift-category-trends
Contract model
  • Additive `/v1` versioning with breaking changes moved to future namespaces.
  • Traceability via model version, training window, build hash, and contract metadata.
  • Reliability fields such as `confidence_score` and `sample_size` on key responses.
  • Partner portal support for quota, usage, invoices, and credential lifecycle.
Concrete platform proof

Not just a model, a governed delivery surface.

Technical evaluators need more than positioning. They need to see a credible API surface, traceability metadata, and partner operations in the product story.

API surfacePartner-ready endpoints
POST/v1/gift-recommendations
POST/v1/gifting-intent
POST/v1/occasion-predictions
Governance layerTraceable intelligence outputs
confidence_score: 0.91
sample_size: 18432
model_version: 2026.03
trace_id: gpi_81x0f2
Partner portalOperational controls in one surface
Quota controls
API keys
Invoices
Audit trail
Integration path

Simple enough to evaluate, structured enough for enterprise teams.

1. Provision partner tenant and role assignments
2. Issue X-Intelligence-Key credentials
3. Integrate trends, recommendation, intent, or occasion endpoints
4. Handle confidence and traceability metadata in downstream systems
5. Use the partner portal for quota, invoices, and API key lifecycle
Why it matters technically

Enterprise teams are not just buying a model. They are evaluating a delivery surface that needs to be governable, trustworthy, versionable, and clear enough to integrate without hidden product debt.

Current posture

The public surface is partner-oriented and invite-only. There is no anonymous self-serve key issuance or generic developer-docs funnel. That is intentional for this stage of the platform.

Request early accessView the platform story