# protocols-pagination-link-checks
render pydantic_v2.BaseModel
  Error: --client-protocols['numbers.next'].continuation.read: The next URL of 'numbers.next' reads integer values, where only string values fit; --client-protocols['status.next'].continuation.read: The next URL of 'status.next' reads integer values, where only string values fit; --client-protocols['nullable.next'].continuation.end: The next URL of 'nullable.next' can read null, which no end condition covers; --client-protocols['nullable.next'].continuation.end[1].value: The end value 1 of 'nullable.next' is integer, which its next URL never reads; --client-protocols['undeclared.next'].continuation.read: The next URL pointer '/after' of 'undeclared.next' names no property of the GET /users response; --client-protocols['bodiless.next'].continuation.repeat_request_body: The next URL of 'bodiless.next' repeats the request body, which GET /users does not take; --client-protocols['undeclared.links'].continuation.header: The links of 'undeclared.links' come from the header 'Link', which POST /searches does not declare; --client-protocols['spaced.links'].continuation.rel: The relation 'next page' of 'spaced.links' is no RFC 8288 relation type: a registered name or an absolute URI; --client-protocols['quoted.links'].continuation.rel: The relation 'urn:"next"' of 'quoted.links' is no RFC 8288 relation type: a registered name or an absolute URI; --client-protocols['written.links'].bindings[2].target: The binding 2 of 'written.links' writes the cookie 'session', which carries credentials no helper writes; --client-protocols['written.links'].bindings[0].target: The binding 0 of 'written.links' writes the query parameter 'limit', which no request after the first sends; --client-protocols['written.links'].bindings[1].target: The binding 1 of 'written.links' gives integer values, which the header parameter 'X-Trace' of GET /users does not accept; --client-protocols['written.links'].bindings[3].target: The binding 3 of 'written.links' writes the same target as its binding 1; --client-protocols['fetched.searches'].bindings[0].target: The binding 0 of 'fetched.searches' writes the request body, which no request after the first sends; --client-protocols['repeated.searches'].continuation.repeat_request_body: The next URL of 'repeated.searches' repeats the request body of POST /searches, which is not safe to send again; declare the operation's retry_safety idempotent; --client-protocols['repeated.searches'].continuation.read: The next URL of 'repeated.searches' reads the header 'X-Next', which POST /searches does not declare; --client-protocols['repeated.searches'].bindings[0].target: The binding 0 of 'repeated.searches' gives integer values, which the property '/token' of the request body of POST /searches does not accept
