support.supper.feed.getCreatorFeed

Get a creator's verified cross-repo support feed: support.supper.feed.post records authored on every supporter repo whose recipient is the named creator, newest first. Every returned post carries a payment strongRef verified against an active broker-attested payment; the AppView never re-derives amount/currency/status. Public read; unverified posts are never returned and outputs carry only public record bodies, never private metadata.

Repository @supper.support did:plc:mcsqdltevtjpu26xthzzmm2l namespace authority
Details · query
Kindquery
Authorityfeed.supper.support
Indexed

Query

query · GET

Parameters

query string

cursor

string

Opaque cursor from a previous response.

  • maxLength: 2048

limit

integer
  • minimum: 1
  • maximum: 100
  • default: 50

recipient

requiredstring · at-identifier

DID or handle of the creator whose support feed to fetch.

Output

application/json

cursor

string
  • maxLength: 2048

posts

requiredarray
itemsref
Reference

#postView

object

Properties

brokerProof

requiredref

Exact current active trusted-broker proof generation returned by ATM's verifier. Clients may resolve payment and brokerProof to independently recompute both record CIDs and the attested payment CID.

cid

requiredstring · cid

CID of the exact feed-post record generation returned in this view.

createdAt

string · datetime

indexedAt

requiredstring · datetime

When the AppView indexed this record.

kind

string
  • maxLength: 32
  • knownValues: tip | subscription | shop-purchase | commission-purchase

payment

requiredref

Exact versioned reference to the attested payment record in its payer-of-record repository. When paymentVerified is true, ATM's exact verifier confirmed this URI and CID plus the active trusted broker proof. Resolve amount/currency against the public payment record; never infer settlement from the Supper post alone.

paymentVerified

requiredboolean

True only when ATM's exact verifier returns this payer-record URI+CID with a current active proof from a trusted broker, and Supper independently authenticates the payment body, attestation CID, broker-proof body, payer, recipient, and collection. A payer plus payment CID can authorize at most one verified Supper post.

recipient

requiredstring · did

Creator/project DID the support is directed at.

supporter

requiredstring · did

Author repo DID of the post (the supporter who paid).

text

string

Optional public supporter-authored message.

  • maxLength: 3000
  • maxGraphemes: 300

uri

requiredstring · at-uri

AT URI of the indexed support.supper.feed.post record.

viaProject

string · did

Similar lexicons

semantic match

Lexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.

  • List the creators a supporter has payment-verified support.supper.feed.post records for across all repos. The cross-repo inverse of feed.listSupporters. Self-authorship alone is not payment evidence. Public read; returns creator DIDs and aggregate counts only, never amounts, emails, or processor identifiers.

  • List the distinct supporter DIDs for a creator across all repos, derived from verified support.supper.feed.post records pointing at the creator. Creator-owned support.supper.entitlement anchors identify unlockable surfaces but do not represent a supporter-to-creator edge. Public read; returns DIDs and aggregate counts only, never amounts, emails, processor identifiers, or private member data.

  • Public, supporter-authored Supper feed post sidecar for a completed support event. This record is presentation/social context only: payment truth remains in the referenced attested payment record, and private checkout, order, fulfillment, buyer contact, commission brief, attachment, and DM data must stay off-protocol.

  • Get a creator/supporter's cross-account Supper page: the indexed support.supper.actor.profile marker plus the actor.about section and all actor.project showcase entries for the account, regardless of which compatible app wrote them. Public Supper AppView read; responses contain only public record bodies and never private metadata or processor identifiers.

  • List a creator's public Supper commerce records across repos: support.supper.membership.program programs, support.supper.membership.tier sidecars, and support.supper.commission offers. Only records authored by the named creator's own repo (creatorVerified) are returned. Public read; membership outputs carry their portable ATM program or tier identity and Supper presentation fields, while catalog product and price data resolve through those ATM records. Outputs never carry processor ids, member l