BlueVetaUpright — Product Photo Rotation Detector
Pricing
from $30.00 / 1,000 rotation detections
BlueVetaUpright — Product Photo Rotation Detector
Detects whether a product photo is sideways or upside-down and returns the exact rotation fix (4-axis plus fine-tilt), each with a calibrated confidence score. Thin proxy to the live BlueVetaUpright API — pay-per-event pricing, no idle compute charged to callers.
Pricing
from $30.00 / 1,000 rotation detections
Rating
0.0
(0)
Developer
Tomer Bar-Meir
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
0
Monthly active users
14 days ago
Last modified
Categories
Features
Share
BlueVetaUpright — Apify Actor
Thin proxy to the live BlueVetaUpright rotation-detection API
(https://blueveta.com/upright), built as an Apify Actor in Standby mode
with pay-per-event pricing — Apify's own docs confirm this is the one
pricing mode exempt from their default revenue-share formula, which
otherwise bills the developer for Apify's own platform compute, not just
real usage. See docs/UPRIGHT_MARKETING_PLAYBOOK.md Section 2.1f for the
real research behind this choice.
What it does
Send { "imageUrl": "https://..." } (optionally "returnImage": true) and
get back the same JSON response blueveta.com/upright's own API returns:
rotationClockwise4Axis, confidence4Axis, rotationClockwiseFull,
confidenceFull, resolved, note, heicConverted, and — when
returnImage was requested — imageBase64/imageMimeType (always the
lossless 4-axis fix only, never the resampled fine-tilt correction, per the
locked product policy in .claude/rules/upright.md item 24).
Charges one detection event per real, successful answer, plus one
image-return event when returnImage was requested — mirrors the direct
API's own 1.5x pricing intent (UPRIGHT_PRICE_TENTHS in
functions/api/_helpers/uprightCredits.js), never charges on a failed
upstream call.
Pricing (final, 2026-11-03 — Tomer's explicit numbers, not yet set live in the Apify Console)
Apify's own docs (docs.apify.com/actors/monetize) confirm their commission is exactly 20% of
Actor revenue — at, not under, the ceiling Tomer set before approving this build. One real nuance:
pay-per-event Actors also have real platform usage costs (infra/proxy/storage) deducted from
payout on top of that 20% — expected to be small here (this Actor does no real inference itself,
it's a thin proxy to BlueVeta's own backend) but not pinned to an exact figure without a live
metered run.
Final: detection event = 3¢; image-return event = +2¢ (so a returnImage=true call totals
5¢). Tomer's own spec: "3c per text and 5c per img rotated. the latter should be (if possible)
both text and pic. not just a pic." Confirmed true by the real code, not just by claim:
handleDetection.js always forwards the upstream endpoint's full JSON body (every text field —
wasAlreadyUpright, rotationClockwise4Axis, confidence4Axis, etc.) regardless of
returnImage; requesting returnImage only ADDS imageBase64/imageMimeType on top, it never
replaces the text fields. So the 5¢ image-return event always delivers both the full text answer
and the rotated image together — there is no "image-only" response shape anywhere in this Actor.
Still needs to be set live in the Apify Console's Publication settings once the account exists
(see Deploying for real, below) — nothing is charging at this price yet.
Status (updated 2026-11-03)
Real account exists, real Actor pushed and building successfully, blocked on Tomer's own billing/profile info before pricing can go live. Real progress this session:
- A fresh shared secret was generated and wired to BOTH sides: (Cloudflare side — still needs Master's next Pages deploy to take effect, same standing gotcha as below) andwrangler pages secret put UPRIGHT_MARKETPLACE_SECRET_APIFY
apify secrets add+.actor/actor.json's ownenvironmentVariablesfield (Apify side — confirmed live by a successful build after wiring it in,@BLUEVETA_UPRIGHT_APIFY_SECRETreference). apify pushsucceeded for real (Actor ID63a4q1jxcUToDU0ya, build0.1.2, "SUCCEEDED") — logged in via the CLI's own official browser device-authorization flow, never via a raw token.- Actor Standby mode is enabled and saved.
- Genuine blocker, needs Tomer's own real info, not filled in on his behalf: the Console's Publishing tab requires (1) a public Apify developer profile and (2) real billing details + a payout method before Monetization (the 3¢/5¢ pricing) can be entered at all.
Earlier (2026-10-29) real backend wiring, still accurate:
functions/api/_helpers/uprightMarketplaces.jshas a newapifyprovider entry (headerx-blueveta-apify-secret).- The Pages secret
UPRIGHT_MARKETPLACE_SECRET_APIFYwas regenerated 2026-11-03 (see above) — a Pages secret only takes effect on the NEXT deploy (see.claude/rules/upright.md's own standing Pages-secret gotcha). Until Master's nextnpm run deploy, a real call from this Actor would fail the same way ApyHub's and Zyla's first tests did (secret not yet live). - Same account-creation boundary as every other platform this project has joined: a real human (Tomer) creates the account; once it exists, working it (updates, responding to reviews, pricing tweaks) is this project's job going forward.
Tests
The real request-handling logic (fetch the source image, forward to our own marketplace
endpoint, decide what to charge) lives in src/handleDetection.js, split out of main.js's
HTTP/Actor-lifecycle wiring specifically so it's testable without a real Apify container or
network access (same pattern as mcp-server/src/detectRotation.js):
node --test src/handleDetection.test.mjs
Local smoke test (once an Apify account + CLI exist)
cd apify-actornpm installBLUEVETA_UPRIGHT_APIFY_SECRET=<the real secret value> npm startcurl -X POST http://localhost:4321 -H 'content-type: application/json' \-d '{"imageUrl":"https://example.com/some-product-photo.jpg"}'
Deploying for real
- Tomer creates an Apify account (or confirms one already exists).
apify login(Apify CLI) from this directory.- Set
BLUEVETA_UPRIGHT_APIFY_SECRETas an Actor environment variable (Apify Console → Actor → Settings → Environment variables) to the exact value set viawrangler pages secret put UPRIGHT_MARKETPLACE_SECRET_APIFY. apify pushto build and deploy, then enable Standby mode and pay-per- event pricing in the Actor's own Publication settings.- Confirm Master has deployed
mainto Pages at least once since the backend change above landed, before running a real test call.


