Загрузка видео...

Не удалось загрузить видео

На главную

API Permissions Clarified …you control every permission yourself. When creating an API key on your exchange, you decide what SUMEX can or cannot do. …withdrawal permissions are NEVER required. SUMEX does not request - and cannot use, any withdrawal rights. …your keys stay encrypted. We don’t see your API...

Sumex_Labs's profile picture

SUMEX | Web3 SuperApp

59,634 subscribers

22,805 просмотров • 8 месяцев назад •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

Комментарии: 0

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

Похожие видео

API Keys are available for all users on Polyester Testnet! Create API Keys on your Main Account or Subaccounts, give them granular permissions, trading limits, and track activity. Creating keys takes seconds, and you can test them using Polyester's API Playground.
0:49

API Keys are available for all users on Polyester Testnet! Create API Keys on your Main Account or Subaccounts, give them granular permissions, trading limits, and track activity. Creating keys takes seconds, and you can test them using Polyester's API Playground.

Polyester

50,800 просмотров • 4 дней назад

You decide what your agent can - and can’t - access. Set permissions. Connect in seconds. Revoke access whenever you want. Your agent. Your rules. Try Agent OS →
0:43

You decide what your agent can - and can’t - access. Set permissions. Connect in seconds. Revoke access whenever you want. Your agent. Your rules. Try Agent OS →

Binance

357,062 просмотров • 2 месяцев назад

🦞 OpenClaw API integration is live in the App! You can now generate an API key using the Agent Key feature and deploy your AI trading agent: 🚧 Set a Budget: Control your agent’s weekly trading limit 🛡️ Secure Access: Choose exactly what the AI sees and does 🤖 Total Control: Approve every trade via chat or stop them all instantly Learn more 👉
0:22

🦞 OpenClaw API integration is live in the App! You can now generate an API key using the Agent Key feature and deploy your AI trading agent: 🚧 Set a Budget: Control your agent’s weekly trading limit 🛡️ Secure Access: Choose exactly what the AI sees and does 🤖 Total Control: Approve every trade via chat or stop them all instantly Learn more 👉

Crypto.com

404,029 просмотров • 7 месяцев назад

Introducing API Keys Public Beta Secure your routes with Clerk's managed API keys. Let your users create and revoke keys with prebuilt UI components.
1:04

Introducing API Keys Public Beta Secure your routes with Clerk's managed API keys. Let your users create and revoke keys with prebuilt UI components.

Clerk

44,978 просмотров • 10 месяцев назад

Polyester Subaccounts are available now on Testnet! Subaccounts let you separate trading strategies, manage separate teams and keep balances organized. Invite members, assign roles, set permissions, create API keys and track performance across all your subaccounts.
0:39

Polyester Subaccounts are available now on Testnet! Subaccounts let you separate trading strategies, manage separate teams and keep balances organized. Invite members, assign roles, set permissions, create API keys and track performance across all your subaccounts.

Polyester

172,378 просмотров • 26 дней назад

Introducing a Text-to-API AI ⚙️ Turn any website into an API with 's /extract. Just describe your API in plain text and get an endpoint you can hit. Another great open-source project by !
0:52

Introducing a Text-to-API AI ⚙️ Turn any website into an API with 's /extract. Just describe your API in plain text and get an endpoint you can hit. Another great open-source project by !

Caleb Peffer (Hiring!)

262,975 просмотров • 1 год назад

🟦 SUMEX BETA TEST - LIVE NOW Our beta test just opened - and it’s happening right now during the community call in Discord. here: The CEO is walking everyone through: • how to claim beta access • how to navigate the platform • how to secure your Beta Tester achievement (rewarded after TGE) ⚠️ Access is extremely limited: only 500 slots. And the counter is dropping every minute since this announcement. If you want to be among the first to touch SUMEX before launch - this is your moment. ...tick tock⌚ The doors are open… and they won’t stay open long. 👉 Join the SUMEX Discord and get in.
0:37

🟦 SUMEX BETA TEST - LIVE NOW Our beta test just opened - and it’s happening right now during the community call in Discord. here: The CEO is walking everyone through: • how to claim beta access • how to navigate the platform • how to secure your Beta Tester achievement (rewarded after TGE) ⚠️ Access is extremely limited: only 500 slots. And the counter is dropping every minute since this announcement. If you want to be among the first to touch SUMEX before launch - this is your moment. ...tick tock⌚ The doors are open… and they won’t stay open long. 👉 Join the SUMEX Discord and get in.

SUMEX | Web3 SuperApp

103,644 просмотров • 9 месяцев назад

Your API keys might not be as safe as you think. If you are storing them in your client-side code, they can be extracted even with clever hiding tricks. Learn how to properly secure your sensitive data →
0:44

Your API keys might not be as safe as you think. If you are storing them in your client-side code, they can be extracted even with clever hiding tricks. Learn how to properly secure your sensitive data →

Chrome for Developers

13,337 просмотров • 9 месяцев назад

Today, we’re introducing permission-scoped API keys. You can now give your agents least-privilege-access based on their responsibility.
1:18

Today, we’re introducing permission-scoped API keys. You can now give your agents least-privilege-access based on their responsibility.

AgentMail (YC S25)

17,906 просмотров • 7 месяцев назад

You can't pretend you care about security if you are still sharing API tokens in .env files or sharing SSH keys. This might be good enough to provide simple access to a resource, but it's a horrible way to do security when it really matters. Look into "Identity-Based Access". The state of the art today is Identity-Based Access. With traditional security, you have to present a key to get access to the resource (an API key, a password, or an SSH key). These are long-lived keys you need to keep secret somehow. If somebody steals your key, they become you and get the same access you had. With Identity-Based Access, you need to prove who you are instead. If you are a human, you can prove this with a passkey, SSO with Google or GitHub, or Multi-Factor Authentication. If you are a computer, you can use AWS IAM, Kubernetes, a cloud service account, or any other trusted environment. Once the system verifies your identity, it checks your permissions and gives you a short-lived credential. Prove identity → Permissions → Short-lived credential → Access The difference here is huge, because those credentials are: • Short-lived • Tied to a specific identity • Scoped to specific permissions • Automatically expired • Much easier to audit In practice, implementing this is as simple as integrating with Teleport, which will handle everything for you. Here is a full explanation of how Teleport works and how you can start using it: Thanks to the Teleport team for partnering with me on this post.
5:46

You can't pretend you care about security if you are still sharing API tokens in .env files or sharing SSH keys. This might be good enough to provide simple access to a resource, but it's a horrible way to do security when it really matters. Look into "Identity-Based Access". The state of the art today is Identity-Based Access. With traditional security, you have to present a key to get access to the resource (an API key, a password, or an SSH key). These are long-lived keys you need to keep secret somehow. If somebody steals your key, they become you and get the same access you had. With Identity-Based Access, you need to prove who you are instead. If you are a human, you can prove this with a passkey, SSO with Google or GitHub, or Multi-Factor Authentication. If you are a computer, you can use AWS IAM, Kubernetes, a cloud service account, or any other trusted environment. Once the system verifies your identity, it checks your permissions and gives you a short-lived credential. Prove identity → Permissions → Short-lived credential → Access The difference here is huge, because those credentials are: • Short-lived • Tied to a specific identity • Scoped to specific permissions • Automatically expired • Much easier to audit In practice, implementing this is as simple as integrating with Teleport, which will handle everything for you. Here is a full explanation of how Teleport works and how you can start using it: Thanks to the Teleport team for partnering with me on this post.

Santiago

20,971 просмотров • 2 месяцев назад

When your crypto is on any centralized exchange — it's not really yours. 🔐🖤 On Celia Wallet your crypto belongs to you and only you. Self custody means nobody can freeze, block or control your funds — not even us. Your keys. Your crypto. Your rules. Download Celia Wallet 👉
1:51

When your crypto is on any centralized exchange — it's not really yours. 🔐🖤 On Celia Wallet your crypto belongs to you and only you. Self custody means nobody can freeze, block or control your funds — not even us. Your keys. Your crypto. Your rules. Download Celia Wallet 👉

Celia Wallet

19,734 просмотров • 2 месяцев назад

Bring Your Own Key (BYOK) is live in JetBrains IDEs! You can now connect your API keys from OpenAI, Anthropic, or any OpenAI-compatible provider, and use them with the AI chat, Junie, and Claude Agent right inside your JetBrains IDE. Learn more in the blog post:
1:03

Bring Your Own Key (BYOK) is live in JetBrains IDEs! You can now connect your API keys from OpenAI, Anthropic, or any OpenAI-compatible provider, and use them with the AI chat, Junie, and Claude Agent right inside your JetBrains IDE. Learn more in the blog post:

JetBrains

25,999 просмотров • 10 месяцев назад

IBKR for Claude Code. Project:VEX gives coding agents like Claude Code and Codex the tools to swap tokens, bridge funds and trade perpetuals. Your keys stay on your machine, and execution follows your permissions. Live on Virtuals Protocol.
0:24

IBKR for Claude Code. Project:VEX gives coding agents like Claude Code and Codex the tools to swap tokens, bridge funds and trade perpetuals. Your keys stay on your machine, and execution follows your permissions. Live on Virtuals Protocol.

Virtuals Protocol

17,584 просмотров • 14 дней назад

Composio CTO Karan Vaidya says giving an AI agent your API key is basically making it public once prompt injection enters the picture: "Even if you use [MCP], across all your apps you have to go and authenticate one after the other. If you use Codex, if you switch to ChatGPT, Claude Code, you'll have to do it all over again." "In some cases where MCPs don't exist, you have to literally share the API keys to the agent, which is definitely not secure. It's kind of giving your API key to public." "At some point the agent will find some link which will have prompt injection, and you'll be in a bad place where your key is gone and all your data is public." "We launched Shared Connections where you can share, let's say, an analytic software across the team, or DataDog for debugging, so you don't have to share one password or API keys to every single person." Composio
2:15

Composio CTO Karan Vaidya says giving an AI agent your API key is basically making it public once prompt injection enters the picture: "Even if you use [MCP], across all your apps you have to go and authenticate one after the other. If you use Codex, if you switch to ChatGPT, Claude Code, you'll have to do it all over again." "In some cases where MCPs don't exist, you have to literally share the API keys to the agent, which is definitely not secure. It's kind of giving your API key to public." "At some point the agent will find some link which will have prompt injection, and you'll be in a bad place where your key is gone and all your data is public." "We launched Shared Connections where you can share, let's say, an analytic software across the team, or DataDog for debugging, so you don't have to share one password or API keys to every single person." Composio

MTS

16,416 просмотров • 1 месяц назад

We know today's developers don't want to deal with endless deployment configs and infrastructure headaches. But convenience should never come at the cost of security. So we designed the next era of deployments: MCP Access Control. Introducing OpenShip MCP Access Control. Let Claude or any MCP compatible agent deploy your apps while you stay fully in control. Give your agent only the permissions it needs: • Deploy specific repositories • Read-only or list-only access • Per-resource permission scopes • Fine-grained access control for every operation Get AI-powered DevOps without giving away the keys. All on your own infrastructure, for free. Just head to the MCP tab → choose your agent → add the OpenShip MCP → authenticate → select the permissions you want to grant → then simply ask it to deploy your repository. Our goal is to make OpenShip fully agent-compatible in the safest way possible. And this is just the beginning. Soon, Claude won't just deploy your apps - it'll become your DevOps engineer, managing deployments, auto-scaling, clustering, and infrastructure maintenance while you remain in complete control. OpenShip 0.5.0 also ships with major stability improvements and tons of bug fixes.
0:47

We know today's developers don't want to deal with endless deployment configs and infrastructure headaches. But convenience should never come at the cost of security. So we designed the next era of deployments: MCP Access Control. Introducing OpenShip MCP Access Control. Let Claude or any MCP compatible agent deploy your apps while you stay fully in control. Give your agent only the permissions it needs: • Deploy specific repositories • Read-only or list-only access • Per-resource permission scopes • Fine-grained access control for every operation Get AI-powered DevOps without giving away the keys. All on your own infrastructure, for free. Just head to the MCP tab → choose your agent → add the OpenShip MCP → authenticate → select the permissions you want to grant → then simply ask it to deploy your repository. Our goal is to make OpenShip fully agent-compatible in the safest way possible. And this is just the beginning. Soon, Claude won't just deploy your apps - it'll become your DevOps engineer, managing deployments, auto-scaling, clustering, and infrastructure maintenance while you remain in complete control. OpenShip 0.5.0 also ships with major stability improvements and tons of bug fixes.

OpenShip

22,443 просмотров • 2 месяцев назад

You can now use AI agents with MEGA, on your terms Run them locally or connect a model you trust. Search, organise, and manage your files using simple prompts. Plus, you stay in control of what the AI can access and what it can do. Privacy first. Always 🔒 See what’s possible:
1:01

You can now use AI agents with MEGA, on your terms Run them locally or connect a model you trust. Search, organise, and manage your files using simple prompts. Plus, you stay in control of what the AI can access and what it can do. Privacy first. Always 🔒 See what’s possible:

MEGA

16,791 просмотров • 7 месяцев назад

Coming soon on XPR Network 🤖 Trading bots usually want your money or your keys. This one gets neither. The problem: automated trading usually means trusting someone. You hand your funds to a platform, or give a bot your keys and hope. If they get hacked or disappear, so does your money. What we built: trading vaults you own. ⚛️ Your vault is an ordinary XPR account in your name. ⚛️ Our bot can call exactly one action on it, trade, inside limits you set: per trade, per day, and what it must always keep. ⚛️ It can't withdraw or send your funds anywhere. Only you can. Your money never leaves your control. Orders don't sit on the DEX: each trade fills and settles back into your vault in the same transaction. So your funds are always in an account YOU control, and you can take them out any time with one signature, even if our servers are down. That's thanks to XPR Network's permission system: a custom permission, tied by linkauth to that one trade action, is all the bot ever gets. Trustless setup: an on-chain contract builds your vault from published, hash-checked code. Before you add a cent, your browser reads the chain and runs 7 checks: that it's the published code, that only you own it, and that the bot can do exactly one thing. We never hold your funds. Why XPR Network: permissions fine-grained enough to lock a bot to one action, no gas fees so small trades make sense, an on-chain order book (Metal X) with on-chain price oracles, and WebAuth Wallet signing with Face ID or Yubikey. Here's a full setup, start to finish 👇 Opening soon to a small group of testers.
2:26

Coming soon on XPR Network 🤖 Trading bots usually want your money or your keys. This one gets neither. The problem: automated trading usually means trusting someone. You hand your funds to a platform, or give a bot your keys and hope. If they get hacked or disappear, so does your money. What we built: trading vaults you own. ⚛️ Your vault is an ordinary XPR account in your name. ⚛️ Our bot can call exactly one action on it, trade, inside limits you set: per trade, per day, and what it must always keep. ⚛️ It can't withdraw or send your funds anywhere. Only you can. Your money never leaves your control. Orders don't sit on the DEX: each trade fills and settles back into your vault in the same transaction. So your funds are always in an account YOU control, and you can take them out any time with one signature, even if our servers are down. That's thanks to XPR Network's permission system: a custom permission, tied by linkauth to that one trade action, is all the bot ever gets. Trustless setup: an on-chain contract builds your vault from published, hash-checked code. Before you add a cent, your browser reads the chain and runs 7 checks: that it's the published code, that only you own it, and that the bot can do exactly one thing. We never hold your funds. Why XPR Network: permissions fine-grained enough to lock a bot to one action, no gas fees so small trades make sense, an on-chain order book (Metal X) with on-chain price oracles, and WebAuth Wallet signing with Face ID or Yubikey. Here's a full setup, start to finish 👇 Opening soon to a small group of testers.

Paul Grey

24,091 просмотров • 1 месяц назад