social networks // decisioning infrastructure

Rank the home feed for every user,
price the sponsored slots in the same order.

The ranking layer between candidate generation and the feed a user opens. Gortex personalizes the home feed and content surfaces per user and places sponsored slots in one call, so your team ships product instead of running a feed ranking stack.

request access → see the decisioning apis

# 01 / the problem

Feed ranking runs on the request path for every user, on every load.

A social feed is ranked fresh per user, per session, per open. The models that decide what a person sees keep changing, and every new content surface needs its own tuning. On top of that, sponsored slots have to be priced against the organic order you just computed, not bolted on beside it. The team that owns the feed keeps rebuilding it, on the hot path, forever.

01 personalized per user, per load

The home feed is re-ranked for every user on every open, so ranking sits on the request path for your highest-traffic surface.

02 latency on the hot path

Feed and content ranking are online, not batch. Every added engagement signal is latency you pay on every feed load, for every user.

03 sponsored slots against the organic order

A sponsored post has to be priced against the feed the user would have seen, not slotted beside it, or the paid slot degrades the surface.

04 no record of why a post ranked

When a creator disputes reach or a placement is questioned, there is often no trace of why a post landed where it did in someone's feed.

# 02 / how gortex fits

One endpoint personalizes the feed and prices its sponsored slots together.

You send a recipient, a surface, and the candidate posts you already retrieved. Gortex returns the per-user order and the sponsored placements in the same response, priced against the organic feed, inside one sub-200ms p99 call. It is the same core that powers the feed ranking api, the content ranking api, and the personalization api, so every surface ranks from one decision layer.

your retrieval

you gather the candidates: posts, reels, stories, and the profiles a user follows.

gortex decides

personalize the feed for that user and price sponsored slots against the organic order, in one call.

your surface

render the home feed with sponsored slots already placed and priced.

01 you keep retrieval

Gortex ranks the candidates you bring from your own graph and stores. No data migration, no re-platforming.

02 ranking and monetization in one call

The per-user order and the sponsored slots resolve against each other, so a paid post only takes a slot when the placement still fits the feed. Ranking and monetization land in one sub-200ms call.

03 every decision is traceable

Each response carries a decision_id and a trace_id. The reason a post ranked for a user is recorded, not reconstructed after a complaint.

04 one core across every surface

The feed ranking api, content ranking api, and personalization api share one decision layer, so the home feed and every content surface rank from the same call.

# 03 / the call

One request. A personalized feed and its sponsored slots.

POST /v1/decide
200 OK · 76ms
 // Personalize a home feed and price its sponsored slots.
$ curl api.gortex.ai/v1/decide \
  -H "Authorization: Bearer $GORTEX_KEY" \
  -d '{
    "recipient": { "id": "u_8120" },
    "context":   { "surface": "home_feed" },
    "items":     [ /* 200 candidate posts */ ]
  }'

{
  "ranked":      [ /* ordered post IDs */ ],
  "sponsored":   [{ "slot": 3, "price": 0.42 }],
  "decision_id": "d_01HXZ3M",
  "trace_id":    "t_01HXZ3N"
} 

# 04 / questions

Social feed ranking, answered plainly.

How does Gortex rank a social feed?

You send the recipient, the surface, and the candidate posts you already retrieved. Gortex returns the personalized order for that user and places sponsored slots in the same response, so home feed ranking and monetization resolve together on the request path.

Do we have to move our data or graph to use Gortex?

No. You keep retrieval and your social graph where it lives. Gortex ranks the candidates you pass in and returns the per-user order plus sponsored slots. There is no re-platforming and no data migration.

Can it price sponsored slots against the organic feed?

Yes. Sponsored slots are priced against the organic order, not beside it, so a paid post only takes a position when the placement fits the feed a user would have seen. It all resolves inside one sub-200ms p99 call.

# 05 / start

See a feed decision for your network, live.

The private beta is by invitation. Tell us the feed and content surfaces you rank, and we will get you a key.

request access → see the decisioning apis view the simulation

Rank the home feed for every user, price the sponsored slots in the same order.