Zendesk

zendesk.com · Debrid, Storage · 3 records · JSON

Hotmart Debrid★ qualifiesemailno cardDwrite-gated
Zendesk Guide (help center article attachments) Storagetrialinstitutionno cardRper-object-cap
streamable (as a durable store) Storagefails: quotaemail?card?R

Hotmart Debrid

★ qualifiesemailno cardDwrite-gated

suportehotmart.zendesk.com/hc/pt-br/articles/25648853025037- · checkout / payment processor used by Brazilian and Spanish-language resellers · debrid/hotmart · JSON · compare

Free tier	Not a service the client buys. Hotmart charges the seller; the buyer pays the product price, with 'taxas especificas que podem ser aplicadas a compras internacionais e de produtos digitais'. unit none; metered on none
Price	none stated
Per-object cap	not applicable: a checkout.
Retention	not applicable.
Egress	not applicable.
Identity	email Email plus a card. The global card section asks only for 'numero do cartao, nome do titular, data de vencimento e CVV'.
Limits	write-gated method availability is set per product by the seller and varies by buyer country; Pix and boleto are listed as Brazil-only source The article states that not all methods reach all buyers: 'cada pais possui taxas especificas que podem ser aplicadas a compras internacionais'.
Binding	write-gated The gate is which methods the seller enabled and which ones the buyer's country allows; a card is the only method that crosses both.
Interface	rest A hosted checkout that adapts by country and converts currency automatically: 'o checkout da Hotmart faz a conversao automatica do valor do seu produto para a moeda do seu comprador'. The seller chooses which methods to enable per product.
Tooling	Browser only, plus subscription and installment products. No client needed.
Composes with	Hotmart is the Spanish- and Portuguese-language checkout most likely to be in front of a reseller that also sells to Spain, Mexico or Argentina, because it settles in more than 180 countries and converts the price. It is the payment path a foreigner is most likely to complete without a Brazilian document.
Reliability	Installments are charged once by Hotmart and split by the buyer's bank, so a refund does not cancel the installments directly with the issuer: 'Depois da aprovacao, nao e possivel cancelar as parcelas diretamente com a operadora.'
Notes	Recorded as a rail, not as a provider: its role is to answer whether a foreigner can pay a Brazilian or Spanish reseller. The answer is yes by card, in a converted currency, subject to the seller having enabled a global method for that product.
Evidence rung	documented The method inventory, the 180-country reach, the global card fields and the Pix-is-Brazil-only classification were read in Hotmart's own help article today, updated 2026-10-19.
Checked	2026-10-24 (live); stale on 2026-11-23

Evidence (3)

date	source	what it proved
2026-10-23	suportehotmart.zendesk.com/hc/pt-br/articles/25648853025037-	'mais de 20 metodos de pagamento, alcancando compradores em mais de 180 paises'
2026-10-23	suportehotmart.zendesk.com/hc/pt-br/articles/25648853025037-	'Metodos de pagamento exclusivos do Brasil > Pix', which places Pix on the Brazilian side of the divide
2026-10-23	suportehotmart.zendesk.com/hc/pt-br/articles/25648853025037-	the global card path and the installment caveat: 'nao e possivel cancelar as parcelas diretamente com a operadora'

More fields (4)

{
 "countries": "180+",
 "methods": "20+",
 "brazil_only_methods": [
  "Pix",
  "boleto"
 ],
 "article_updated": "2026-10-19"
}

Zendesk Guide (help center article attachments) Storage

trialinstitutionno cardRper-object-cap

www.zendesk.com · paas · storage/zendesk-guide · JSON · compare

Free tier	'Each article has no limit on overall storage or total number of attached files.' Per-file 20 MB. But account-level file storage is separately capped at 10 GB base + 2 GB/agent (Team) — the article-level 'no limit' sits inside that account bucket. unit GB; metered on stored-bytes
Price	none stated
Per-object cap	20 MB per file (20000000 bytes)
Retention	not stated
Egress	Free and unranged-open. Article attachments are served from `support.zendesk.com/hc/article_attachments/<id>` with no auth, no referer check, `Accept-Ranges: bytes`, `Access-Control-Allow-Origin` permissive, `x-amz-replication-status: COMPLETED`, AES256 at rest.
Identity	institution derived from the record's prose, not from an identity field, and no signup was executed: file storage 10 GB base + 2 GB/agent. request-rate: Guide API is rate limited; an unauthenticated write probe `POST /api/v2/help_center/articles.json` returned 403 (good — no open w
Limits	per-object-cap 20 MB per file source per-object-cap: 20 MB per file/image in articles (2 MB for community images). Quota: account file storage 10 GB base + 2 GB/agent. request-rate: Guide API is rate limited; an unauthenticated write probe `POST /api/v2/help_center/articles.json` returned 403 (good — no open write). Retention: archived tickets still count toward storage.
Binding	per-object-cap the per-object cap sets the shard size and therefore the object count; it bounds the total more tightly than any headline quota
Interface	rest, cli rest
Tooling	Help Center API (`/api/v2/help_center/articles/{id}/attachments.json` returns the public `content_url`). Third-party CLI `tukaelu/zgsync` adds a Guide media subcommand.
Composes with	20 MB per file x unbounded attachments per article, but the 10 GB account file-storage pool is the wall. Trial-only for a free account, so the multiplier is trial instances, which is a bad trade.
Reliability	The read path is the cleanest in this whole niche — public, ranged, unauthenticated, no expiry — but Zendesk has no free plan (14-day trial), so it cannot be a free-storage answer, only a pattern to copy.
Notes	'Each article has no limit on overall storage or total number of attached files.' Per-file 20 MB. But account-level file storage is separately capped at 10 GB base + 2 GB/agent (Team) — the article-level 'no limit' sits inside that account bucket.
Evidence rung	reported One page read moves it to documented.
Checked	2026-10-21 (inherited); stale on 2026-11-04
Parsed numbers	`$.limits[0].value` limit:per-object-cap 20.0 MB

Evidence (4)

date	source	what it proved
2026-10-21	support.zendesk.com/hc/en-us/articles/4408884048794-	... — 'Articles: 20MB limit per file or image upload' and 'Each article has no limit on overall storage or total number of attached files'
2026-10-21	support.zendesk.com/hc/en-us/articles/4408835043994-Managing	default storage '10 GB base' + '2 GB per agent' (Team)
2026-10-21	support.zendesk.com/hc/article_attachments/11203045835930	probe: GET -> 200, 365,146 bytes, image/png, no referer/UA needed (also 200 with `curl/8`), `Range: bytes=0-99` -> 206
2026-10-21	withheld	probe: 8 parallel ranged GETs x 45,000 B -> all 206, 360,000 B in 0.63 s

More fields (1)

{
 "dead_end": {
  "failure_class": "quota",
  "why": "'Each article has no limit on overall storage or total number of attached files.' Per-file 20 MB. But account-level file storage is separately capped at 10 GB base + 2 GB/agent (Team) — the article-level 'no limit' sits inside that account bucket.",
  "retry_when": null,
  "first_recorded": "2026-10-21"
 }
}

Unknown or withheld values (6)

$.evidence[3].url private-url
$.extras.dead_end.retry_when process
$.free_tier.notes process
$.per_object_cap.notes not-extracted
$.retention.notes not-extracted
$.retention.stated not-extracted

streamable (as a durable store) Storage

fails: quotaemail?card?R

streamable-support.zendesk.com/hc/en-us/articles/35415717293 · rejected-provider · storage/streamable-2 · JSON · compare

Free tier	Listed as a candidate for completeness but the 90-day auto-deletion is disqualifying on its own — a storage target that erases content on a timer is not storage. unit none; metered on none
Price	none stated
Per-object cap	not recorded
Retention	not recorded
Egress	not recorded
Identity	email (placeholder) not published
Binding	none no constraint of a named kind was recorded; the verdict rests on the quota sentence rather than on a named limit
Interface	unknown
Tooling	not recorded
Composes with	not recorded
Reliability	Listed as a candidate for completeness but the 90-day auto-deletion is disqualifying on its own — a storage target that erases content on a timer is not storage.
Notes	Listed as a candidate for completeness but the 90-day auto-deletion is disqualifying on its own — a storage target that erases content on a timer is not storage.
Evidence rung	reported
Checked	2026-10-21 (inherited); stale on 2026-11-04

Evidence (1)

date	source	what it proved
2026-10-21	streamable-support.zendesk.com/hc/en-us/articles/35415717293	Listed as a candidate for completeness but the 90-day auto-deletion is disqualifying on its own — a storage target that erases content on a timer is not storage.

More fields (1)

{
 "dead_end": {
  "failure_class": "not-storage",
  "why": "Listed as a candidate for completeness but the 90-day auto-deletion is disqualifying on its own — a storage target that erases content on a timer is not storage.",
  "retry_when": "never; it is not storage",
  "first_recorded": "2026-10-21"
 }
}

Unknown or withheld values (14)

$.chaining not-recorded
$.confidence_note withheld
$.egress.terms not-recorded
$.free_tier.notes process
$.identity_cost.detail defaulted
$.identity_cost.kind identity-defaulted
$.interface interface-unknown
$.interface_detail withheld
$.limits_note process
$.per_object_cap.notes not-recorded
$.per_object_cap.stated not-recorded
$.retention.notes process
$.retention.stated not-recorded
$.tooling not-recorded