What is kept for compatibility

Each field, key, answer, address and MCP tool name kept answering for compatibility, with what replaces it. The fund addresses and the tool names are read from the code that answers them. Nothing listed here is removed inside v1.

get/deprecations.json

Request

  • Base URL: https://tickerinside.com/api/v1
  • URL: https://tickerinside.com/api/v1/deprecations.json
  • Auth: none required

Response

The file. The example is a real answer, shortened: long lists and maps keep their first entries.

countnumber nullable required

How many entries.

rulestring nullable required

What deprecated means here, in one sentence.

aliasesobject required

Each fund address the Worker answers with a 301 to the fund's file under its new ticker: {old ticker: new ticker}, lower case, as src/index.js lists them.

contractstring nullable required

The data contract this file belongs to: /contract/.

docsstring nullable required

Where this file is documented.

licensestring nullable required

The licence the file is published under.

attributionstring nullable required

How to credit the data: a link to this file where the medium allows one, the name where it does not.

Changes

No recorded changes to this operation across all 1 revision of this API.