Comparisons
Us and Secta, from the IT department’s side
Where an AI headshot tool meets IT: our API, signed webhooks, OIDC single sign-on and two-factor. On Secta, as of September 2026, see their site.
From $39 per person, volume discounts from 5 people.
- 40 headshots per person
- About an hour from selfies to download
- Nobody on the team needs an account
Secta is an established AI headshot product and, on its own site, offers plans for teams alongside those for individuals. We have not verified what it offers today, so as of September 2026 this page states nothing about its features, prices or integrations; their site is the place for that. What we can describe in detail is the part of a purchase that an IT or operations team owns: how the product is driven programmatically, how administrator access is protected, and which languages the whole thing is published in.
Comparing
What to check before you choose.
The questions a team buyer should put to any headshot tool, and how Starkie Teams answers them. For the other tool, check their current site.
| What to check before you choose. | Starkie Teams | The other tool |
|---|---|---|
| One-time credits, no subscription | Yes | See their site |
| 40 headshots per person | Yes | See their site |
| One style enforced across the whole team | Yes | See their site |
| Teammates need no account | Yes | See their site |
| Admin approval before photos go out | Yes | See their site |
| Consent text versioned and logged per person | Yes | See their site |
| API and signed webhooks | Yes | See their site |
| Published in English and Italian | Yes | See their site |
What we will and will not assert
It would be easy to write a paragraph implying that a competitor lacks an API, and impossible to defend it a month later. So the rule on these pages is simple: we describe our own interfaces, and we point at the other vendor for theirs.
If an integration matters to your rollout, the productive move is to ask both sides for endpoint documentation and to check whether it is public. Public documentation is itself a signal, because it is a commitment somebody has to keep working against after the sale.
The result
Everyone, in the same light.
Choose a backdrop and an outfit once. Every person who joins is generated inside that style, so the team page finally looks like one team rather than a collage of whoever had a photo.
Sample headshots generated by Starkie from phone selfies.
Driving it from your own software
An organisation issues API keys with a read or write scope and calls a JSON API over ten endpoints: the organisation profile, the credit balance, listing members with filters and paging, creating and inviting up to fifty at a time, fetching a member, reminding, granting a retry, listing a member’s images and fetching their branded profile picture, and creating an open invite link.
Six event types are delivered to registered endpoints as signed requests, retried with backoff, and any delivery can be replayed by hand. The endpoint reference is published, not sent on request.
{
"type": "member.photos_ready",
"organizationId": "org_…",
"data": { "memberId": "cle…" }
}What the organiser sees
The whole run, from one screen.
Invites, consent, approval, downloads and the branded profile pictures, each a step in the same place.
- Invite peoplePaste emails or upload a CSVOpen linkCopy linkstarkie.ai/teams/join/x7q…Only @acme.com addresses24 invited
- DownloadsWhole team, one archive24 people · 960 files
- One folder per person
- Approved people only
- ReviewLena40 headshotsAwaiting approval
ApproveRequest a retakeReasonThe tie: could we try the open collar? - Branded profile pictureACMECompany frame1024 · 512
Re-rendered when the template changes
- Before you uploadConsent text v3
Your selfies are used to generate your headshots and deleted at the end of the retention period.
I agreeAccepted · logged - Webhookmember.photos_readyDelivered
X-Starkie-Signature: t=1700000000,v1=5257a8… · Signed{ "type": "member.photos_ready", "organizationId": "org_…", "data": { "memberId": "cle…" } }
Who can sign in, and in which language
Administration can be placed behind an organisation’s own identity provider using OIDC single sign-on, with a single provider registered against each organisation and a domain claimed by one organisation only, and time-based two-factor is available for the owner and admin roles.
Employees never sign in, so there is no employee directory to provision or deprovision. The product, including the screens an employee sees and the emails they receive, is published in Italian and English, which matters when a rollout crosses a border and half the recipients would otherwise be reading a second language.
Backdrops
- Studio white
- Studio greySelected
- Studio black
- Modern office
- Glass office
- City street
- Library
- Navy gradient
Outfits
- Dark suit
- Light suit
- Blazer, no tieSelected
- Fine knit
- Casual shirt
- White coat
The difference
A shoot day, or an afternoon.
Booking a photographer
- Find a date the whole team can make
- Book a room and a photographer
- Chase the people who were travelling
- Wait for retouched files
- Start again for every new hire
With Starkie Teams
- Invite by email, CSV or one link
- Everyone uploads selfies from a phone
- Remote colleagues take part on the same terms
- 40 headshots each in about an hour
- New hires get the same style, whenever they join
Pricing
One credit per person. Discounts stack as you buy.
No subscription and no seats. A credit is one person’s 40 headshots, and the discount on every purchase is set by the credits you have bought so far.
- First 4 creditsList price$39.00 each
- 5+ credits20% off$31.20 each
- 25+ credits30% off$27.30 each
- 100+ credits40% off$23.40 each
- 250+ credits50% off$19.50 each
Estimate your price
- Price per person
- $31.20
- Volume discount
- 20%
- Subtotal
You're in the 20% band. 15 more people reaches 30%.
Prices in US dollars. One credit per teammate.
Trust
Read it before you buy.
The documents a procurement or IT team asks for, published rather than sent on request.
- Data Processing AgreementRoles, sub-processing, retention and deletion, in writing.
- Sub-processorsEvery third party that touches a photo, and why.
- SecurityHow photos are stored, who can open them, and for how long.
- Privacy notice for teamsWhat each teammate is told before they upload a selfie.
- GDPRRights, requests, and how to exercise them.
Frequently asked questions
How are webhook payloads authenticated?
Each request carries a timestamped HMAC signature over the raw body, plus headers naming the event type and the delivery. The published documentation includes a verification snippet, and the receiving endpoint must be an https address that is not an internal or loopback host.
Can a key be limited to read-only?
Yes: keys carry a read or a write scope, write implies read, and a key can be revoked at any time from the settings tab. Only a hash of the key is stored, so a lost key is replaced rather than recovered.
Does single sign-on apply to employees too?
No, and that is intentional. Employees hold no account and reach only their own private link, which keeps them out of the identity system entirely. Single sign-on covers the people who administer the organisation and can see galleries and downloads.
What if we need SAML rather than OIDC?
Only OIDC is supported today, and we would rather say so on a comparison page than let it surface during an implementation. It is worth asking every vendor on your list the same question and writing down the answer with the date beside it.
Give the whole team the same headshot, without the shoot day.
Free to set up: you only pay when you buy credits. There is no subscription, and you don't need a card to start.