Working today, built by you, or not built yet. Every case says which.
These are integration patterns for your own buyer and seller journeys. The samples use the real request and response shapes with made up listings; nothing on this page calls the API.
Orbit is PCIFIC's listing generator: a few words and photos in, a complete draft out for the seller to review.
Working API today
The seller types what they are selling and adds photos. Orbit researches the item, then returns a title, description, condition, attributes and a researched price, already scored by the seller review. The seller edits the draft instead of writing from a blank form, and nothing publishes without them.
Uses: POST /api/v1/listings with notes, details and photos.
{
"notes": "iPhone 13, good condition, works fine. Selling my old phone. No box. Collection preferred. Asking £315.",
"details": {
"price": {
"amount": 31500,
"currency": "GBP"
}
},
"images": [
"3f1c2a9e-5b7d-4e21-9c0a-6d8f4b1e7a52"
]
}{
"status": "working",
"processing": true,
"deadlineAt": "2026-10-15T10:01:00Z",
"parts": {
"listing": "pending",
"price": "off",
"safeguard": "off",
"faq": "off"
},
"publishReady": false,
"runId": "8d0e5f12-7a3c-4b96-8e41-c2d9a6f03b75",
"tryThis": "Read where it is with GET /api/v1/listings/8d0e5f12-7a3c-4b96-8e41-c2d9a6f03b75 in a few seconds.",
"warnings": []
}Measure it on your own listings
One call returns the whole draft, so the seller's work becomes reviewing rather than typing. We do not publish a speed figure: we have no repeatable benchmark yet, and time depends on photos, research and the model tier. Every run is timed, so measure it on your own listings: the dashboard's Logs page shows how long each step of each run took. Send the same listing with modelTier ultra-fast to compare the tiers on your data.
Uses: The Logs page in your dashboard, and modelTier standard or ultra-fast on the request.
Working API today
Ask for includeFaq when the draft is generated and Orbit adds three to five buyer questions and answers written from the listing, saying plainly when the listing does not cover something. It happens at draft time only: there is no call that writes an FAQ for a listing that is already published.
Uses: POST /api/v1/listings with includeFaq: true; the answer arrives as listing.faq.
Safeguard closes the information gap between buyer and seller. It reads a listing the way a careful buyer would, shows the seller what is missing or unclear, and shows the buyer what the listing confirms, what it does not, and what to ask before paying.
Safeguard is not fraud prevention. It reads only what you send: the listing's title, description, price, condition, item specifics and up to twelve photos, and it can search the web about the item, never the seller. It cannot inspect or authenticate an item or check seller history, so a high score means the listing is complete and consistent, not that the item is genuine. For valuable items, verify in person or through an authentication service.
Working API today
Once a seller finishes a draft (with Orbit or by hand), send the finished listing to the buyer check and show the seller how a careful buyer will read it before it goes live. The risks and questions tell them what to add.
Uses: POST /api/v1/safeguard/reviews with the finished listing and its photos.
{
"category": "Phones",
"listing": {
"title": "iPhone 13 128GB, good condition, works fine",
"description": "Selling my old phone. No box. Collection preferred.",
"brand": "Apple",
"model": "iPhone 13",
"storage_gb": 128,
"condition": "Good",
"price": {
"amount": 31500,
"currency": "GBP"
}
},
"images": [],
"requirePhotos": false,
"review": true,
"faq": false
}{
"status": "done",
"reviewId": "1f9380fa-a135-4b3d-ab70-1dc1fc50f065",
"score": 6,
"passed": false,
"minimumScore": 7,
"verdict": {
"name": "Caution",
"meaning": "review"
},
"banned": {
"isBanned": false,
"reason": null
},
"review": {
"summary": "Clear model and storage, but the battery health and lock status are missing.",
"fixes": [
{
"field": "/battery_health",
"importance": "important",
"problem": "Battery health is not stated.",
"fix": "Add the battery health percentage from Settings."
},
{
"field": "/description",
"importance": "important",
"problem": "It does not say whether the phone is unlocked.",
"fix": "Say whether the phone is unlocked or tied to a network."
}
]
},
"questions": [
"Has the screen or battery ever been replaced?"
],
"sellerQuestions": [
{
"id": "q1",
"question": "What is the battery health percentage?",
"field": "/battery_health"
},
{
"id": "q2",
"question": "Is the phone unlocked or tied to a network?",
"field": "/description"
}
],
"listing": {
"title": "iPhone 13 128GB, good condition, works fine",
"description": "Selling my old phone. No box. Collection preferred.",
"brand": "Apple",
"model": "iPhone 13",
"storage_gb": 128,
"condition": "Good",
"price": {
"amount": 31500,
"currency": "GBP"
}
},
"pcific": {
"release": "2.0.0",
"category": "Phones",
"schemaVersion": 3,
"prices": {
"/price": {
"amount": 31500,
"currency": "GBP",
"display": "£315.00"
}
},
"warnings": []
},
"expiresAt": "2026-10-19T10:30:00Z"
}A pattern you build on the working API
Run the buyer check on new or reported listings in a background job, then route by band.meaning: pass goes live, review goes to your moderation queue, block is held. The queue, the reviewers and the decisions stay in your marketplace; PCIFIC only supplies the reading and the reasons.
Uses: POST /api/v1/safeguard/reviews; route on band.meaning (pass, review, block).
Working API today
Put a check button beside the price. The buyer sees the verdict, the risks and the reassurance before they commit. A no code hosted page at your-name.pcific.co.uk/safeguard is coming soon.
Uses: POST /api/v1/safeguard/reviews.
Working API today
Every check returns questionsToAsk and a polite sellerMessage the buyer can paste into your messaging. Show them under the verdict so the buyer asks about the gaps before paying.
Uses: questionsToAsk and sellerMessage in every Safeguard response.
Not built yet
No endpoint answers a buyer's free text question about a published listing yet. The nearest today is Orbit's includeFaq at draft time, which answers common questions in advance.
PixelTrace fingerprints listing photos and tells you when a new photo is similar to one registered before in your own marketplace. Your photos are never shared with other marketplaces.
A match means a similar photo was registered before. It can indicate image reuse; it is not, by itself, proof of who owns the photo, of fraud or of wrongdoing. Treat it as a cue for a person to review.
Working API today
Before publish, send each photo to the check. A match goes to a person to review, never an automatic block. Register photos once the listing is live and remove them when it comes down, so matches stay accurate.
Uses: POST /api/v1/pixel-trace/check, then /register on publish and /unregister on removal. Works with any key; a test key checks a separate test registry.
Working API today
Open PCIFIC's hosted camera page on the seller's phone, download the photos to build the listing, and complete the session on publish to get a public certificate link for the listing page. The certificate records a camera session, not proof of ownership.
Uses: POST /api/v1/pixel-trace/captures, then /complete on publish and /retract on removal.
Coming soon
In PCIFIC's own marketplace, Findr lets a buyer post the item they are looking for, and sellers reply with a matching listing of their own. It is not available to license yet. If your buyers would use it, tell us and we will let you know when it is.
Tell us where it should sit and we will scope it with you.