canonical: https://jentic.com/apis/timedoor.io/timedoor # Time Door API A scalable, resilient, and fully documented API for integrated time series analysis. Provides anomaly detection (point and collective), matrix profile computation, missing value imputation, data transformations, forecasting, changepoint detection, motif discovery, pattern chain analysis, serial dependency analysis, spectral analysis, and causal relation inference. The API exposes 9 endpoints secured with apiKey authentication. ## For AI agents Programmatically detect anomalies in time series data, compute matrix profile. Covers 9 operations with apiKey authentication. ## Scope Does not handle payments, communications, or crm - use for social media only. ## Capabilities - Detect anomalies in time series data - Compute matrix profile - Impute missing values - Apply data transformations - Generate time series forecast - Discover motifs in time series ## Use cases ### Social Media Operations Use the Time Door API to perform social media operations programmatically. The API provides 9 endpoints covering core functionality including detect anomalies in time series data, compute matrix profile, impute missing values. Example prompt: Call POST /anomaly to detect anomalies in time series data ### Automated Anomaly Detection Management Automate anomaly detection operations by combining multiple Time Door API endpoints. Agents can compute matrix profile and then impute missing values in a single workflow. Example prompt: Call POST /matrix-profile to compute matrix profile, then verify the result ### AI Agent Integration via Jentic AI agents discover and call Time Door API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually. Example prompt: Search Jentic for 'detect anomalies in time series data', load the operation schema, and execute with Jentic-managed credentials ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/anomaly` | Detect anomalies in time series data | | POST | `/matrix-profile` | Compute matrix profile | | POST | `/impute` | Impute missing values | | POST | `/transform` | Apply data transformations | | POST | `/forecast` | Generate time series forecast | | POST | `/changepoint` | Detect changepoints | | POST | `/motif` | Discover motifs in time series | | POST | `/spectral` | Perform spectral analysis | ## Key resources - **Anomaly Detection** — Detect collective and point anomalies in time series data - **Matrix Profile** — Compute matrix profiles for time series similarity analysis - **Imputation** — Impute missing values in time series data - **Transformation** — Apply data transformations to time series - **Forecasting** — Generate forecasts for time series data ## Why Jentic - **Setup:** Wiring the Time Door API by hand means setting its X-API-Key header, formatting time-series payloads for each analysis endpoint, and handling retries yourself. Through Jentic you install once, import Time Door from the API Directory, store the API key once, and your agent calls it. - **Permission scoping:** Time Door takes its target series in the request body rather than the URL path, so scope the agent by the operations it needs, such as anomaly detection or forecasting. You choose that set, so operations like changepoint or spectral analysis are only available if you include them. - **Credential handling:** Your Time Door API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'detect anomalies in a series' or 'forecast future values', and Jentic returns the matching Time Door operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Facebook** — Alternative social media API - **Twitter** — Alternative social media API - **Linkedin** — Complementary social media API ## FAQ ### What authentication does the Time Door API use? The Time Door API uses an API key passed in the `X-API-Key` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context. ### Can I detect anomalies in time series data with the Time Door API? Yes. Use the POST /anomaly endpoint. The API returns structured JSON responses that agents can parse and act on directly. ### What are the rate limits for the Time Door API? Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer. ### How do I detect anomalies in time series data through Jentic? Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'detect anomalies in time series data'. Jentic returns the matching Time Door API operation with its input schema. Load the schema and execute the call - credentials are injected automatically. ### How many endpoints does the Time Door API have? The Time Door API exposes 9 endpoints covering anomaly detection, matrix profile, imputation operations. ### Can I limit what my agent is allowed to do with the Time Door API? Yes. Because you run Jentic One yourself, your own rules decide which Time Door operations and credentials the agent may use, and the API takes its target series in the request body rather than the URL path, so you scope the agent by the operations you grant it. You can allow just anomaly detection and forecasting while withholding others, so calls like changepoint detection or spectral analysis are only reachable if you include them. The stored API key is injected at execution time and never enters the agent's context.